Why do YouTube views freeze at 301?
Summary
TLDR在这段视频脚本中,Brady Haran 探讨了 YouTube 视频的观看次数计数问题,尤其是数字 301 的神秘现象。Ted Hamilton,YouTube Analytics 的产品经理,解释了观看次数的统计过程以及为何当视频观看次数达到 301 时会暂时冻结。这涉及到对大量观看次数进行统计验证,以确保没有虚假观看。此外,还讨论了代码编写中的一个错误,导致计数器在达到 300 后错误地增加到 301 而不是停止。这段对话揭示了 YouTube 计数系统背后的技术细节和一些有趣的事实。
Takeaways
- 🔢 YouTube视频的观看次数在达到301时会暂停更新,这是由于系统开始进行统计验证过程。
- 🕒 观看次数在301暂停可能是半天到一天,以完成对真实观看次数的验证。
- 🤔 观看次数的统计涉及到全球不同服务器的日志收集和聚合。
- 🛑 视频观看次数被视为一种“货币”,因此需要通过严格的统计验证来排除虚假观看。
- 💡 观看次数的统计和验证过程是自动化的,由计算机完成,而非人工。
- 📈 当视频观看次数少于300时,系统不需要太严格的统计验证。
- 🔄 观看次数的统计问题部分源于全球不同地点的视频缓存和请求响应。
- 👨💻 代码中的一个逻辑错误导致了观看次数在达到300时不是立即停止,而是增加到301。
- 🌐 由于全球服务器的同步问题,有时观看次数可能会超过301,达到302、305或310等。
- 🔄 系统在统计验证后,所有额外的观看次数会累积并显示在视频的总观看次数上。
- 📹 这段对话来自Numberphile频道,讨论了YouTube观看次数统计的内部机制和301现象。
Q & A
为什么YouTube视频的观看次数会在301时暂停计数?
-YouTube视频的观看次数在301时暂停计数是因为YouTube有一个统计验证过程。当视频观看次数超过300时,系统需要进行统计验证以确保观看次数是真实的,这个过程需要一些时间。
YouTube上的'观看次数'是如何定义的?
-在YouTube上,'观看次数'被定义为由实际用户请求的视频播放,并且用户得到了他们想要的内容并拥有良好的用户体验。YouTube将观看次数视为一种'货币',因此需要努力消除虚假的观看次数。
YouTube是如何防止虚假观看次数的?
-YouTube通过统计验证过程来防止虚假观看次数。这个过程中,系统会检查并验证观看次数,以确保它们是真实的,防止机器人或其他方式人为增加观看次数。
为什么YouTube视频在全球不同服务器上缓存?
-YouTube视频在全球不同服务器上缓存是为了提高视频加载速度和用户体验。这样,当用户请求视频时,视频数据不需要从很远的地方传输,而是从最近的服务器提供。
YouTube视频的日志是如何收集和处理的?
-当用户观看视频时,服务器会在日志中写入一条消息。定期地,这些日志会被收集到中央日志收集区域,然后聚合在一起进行计数。
为什么YouTube视频的观看次数有时会在302或305等数字上暂停?
-这可能是因为在全球不同服务器上的日志同时更新到中央数据库时,可能会有多个观看次数同时被计入,即使它们已经超过了301。这是由于代码中的'小于或等于'逻辑导致的。
YouTube视频的观看次数冻结是否意味着实际观看次数被遗漏了?
-不会,YouTube视频的观看次数冻结并不意味着实际观看次数被遗漏。一旦完成统计验证,所有在验证期间累积的额外观看次数都会被添加到总观看次数中。
为什么YouTube视频的点赞数不会像观看次数那样冻结?
-点赞数没有像观看次数那样经过同样严格的统计验证过程。点赞数的数量较少,因此系统可以更容易地处理它们,而不会出现像观看次数那样的冻结现象。
YouTube视频的观看次数冻结是否对视频的推广有影响?
-观看次数冻结可能会让一些用户感到困惑,但它不会影响视频的实际推广效果。一旦统计验证完成,真实的观看次数会被正确反映。
YouTube视频的观看次数冻结现象是否是一个bug?
-观看次数冻结现象并不是一个bug,而是YouTube设计的一个特性,用于确保观看次数的真实性和准确性。
为什么YouTube视频的观看次数会在达到一定数量后进行统计验证?
-当视频观看次数达到一定数量后,YouTube会进行统计验证以确保这些观看次数是真实的,防止虚假观看次数对视频排名和推广造成影响。
Outlines
📊 YouTube视频播放量的秘密
Brady Haran介绍了YouTube视频播放量在301这个数字停滞的现象,这引起了许多观众的好奇。他解释了当新视频上传后,播放量会迅速增加到301,然后冻结一段时间。这一现象让许多人感到困惑,促使他们要求Numberphile调查原因。
👨💻 解析YouTube播放量统计机制
YouTube产品经理Ted Hamilton解释了视频播放量统计的基本机制。他提到,YouTube将播放量视为一种货币,因此需要努力消除虚假播放量。他还谈到,视频通常会分布在全球不同的服务器上,这使得播放量统计变得更加复杂。
🔍 301停滞现象的根本原因
Ted Hamilton进一步解释了为什么播放量会停滞在301的原因。随着播放量超过300,YouTube开始进行统计验证,这一过程需要时间,导致播放量不再逐个增加,而是批量更新。这个验证过程旨在确保播放量的真实性,防止机器人或误导性内容产生的虚假播放量。
⚙️ 代码中的关键细节
Ted Hamilton解释了为何播放量会停在301的技术原因。原本的代码逻辑中使用了“<=300”这一条件判断,导致播放量在达到301时才停止。这种逻辑错误使得播放量卡在了301,直到YouTube完成验证过程。
🌍 全球服务器同步导致的变化
Brady Haran解释了为什么有时播放量会停在302、305甚至310。这是因为来自不同地区服务器的播放记录同时更新至中央数据库,导致多个播放量同时被计入,从而使得最终停滞的数字有所不同。
🎥 播放量冻结带来的困扰
Ted Hamilton提到,播放量冻结现象虽然没有引起严重问题,但确实让人感到不便,尤其是当点赞数与播放量不匹配时。尽管如此,这一现象也促成了像这类视频的诞生,帮助观众更好地理解YouTube的工作原理。
🕵️ 更多细节即将揭晓
Brady Haran透露,他与Ted Hamilton的对话还有更多未公开的内容,尤其是关于播放量定义的进一步探讨。他表示将很快在Numberphile频道上传这些内容。对于不喜欢与计算机或互联网相关话题的观众,他也承诺未来会有更为多样的内容。
Mindmap
Keywords
💡Numberphile
💡YouTube view counter
💡Ted Hamilton
💡Counterfeit views
💡Cache
💡Log collection
💡Statistical verification process
💡Batch increment
💡Code logic
💡Idiosyncrasy
💡Simultaneous update
Highlights
YouTube上的301现象:新视频上传后,观看次数达到301时会暂时冻结。
Ted Hamilton,YouTube Analytics的产品经理,解释了这一现象。
YouTube的观看次数被视为一种“货币”,需要严格防止虚假观看。
视频在全球范围内的缓存分布增加了观看次数统计的复杂性。
当视频观看次数超过300时,YouTube会启动统计验证过程。
301现象的产生是因为代码逻辑错误,将“小于300”误写为“小于等于300”。
代码编写者可能没有意识到这一逻辑错误对YouTube的巨大影响。
有时观看次数会停在302、305或310,这是由于全球服务器同时更新造成的。
视频的点赞数不会经过与观看次数相同的严格统计过程。
观看次数的暂时冻结可能导致一些尴尬的情况,例如视频有2000个赞却只有300次观看。
Brady Haran计划在未来上传更多关于YouTube观看次数的详细讨论。
观看次数的统计和验证过程是为了防止机器人刷量或误导性标题和缩略图带来的影响。
YouTube的观看次数统计系统是为了防止虚假观看而设计的。
观看次数的暂时冻结是YouTube的一个独特现象,由代码逻辑错误引起。
Ted Hamilton提到,尽管301现象引起了许多疑问,但它更多被视为一种烦恼而非严重问题。
Brady Haran和Ted Hamilton的对话深入探讨了YouTube观看次数统计的工作原理。
Numberphile频道通过这次访谈揭示了YouTube背后的技术细节和决策过程。
Transcripts
BRADY HARAN: I want to deal with a number that must be the
most requested so far on Numberphile, and that is 301.
Now, for those of you who don't pay much attention to
the YouTube view counters, you might wonder what the big deal
is with 301, and let me tell you.
When a new video is uploaded, and if it's quite a popular
one, you'll quickly see the view counter rise and rise and
rise, and then it will get to 301, and it will freeze.
And it will stay on 301 for a day, maybe half a day, and
then it will start counting to higher numbers as usual.
Now, a lot of people have been very mystified by this, and
have asked us to check it out.
TED HAMILTON: I'm Ted Hamilton, I'm a product
manager for YouTube Analytics.
BRADY HARAN: So there you go.
I've got in touch with the people who actually count the
YouTube views.
TED HAMILTON: That is correct.
Well, we actually have the computers do it.
We don't count them ourselves, but yes.
BRADY HARAN: So before we get to this whole 301 malarkey,
what is a view on YouTube?
I've always wondered.
is someone just pressing play counting as a view?
TED HAMILTON: Well, that's actually a bit
of a YouTube secret.
A view should be a video playback that was requested by
an actual user who got what they were intending to get and
had a good user experience.
We think of views as a currency, and therefore we
have to make a significant effort to eliminate
counterfeit views, if you will.
BRADY HARAN: Now, I know that all sounds a bit mysterious,
and we will come back to it later on in the video, but
let's crack on with this 301 figure.
And you're going to find out counterfeit views actually
have a bit to do with it.
But the next thing we need to realize is when you watch any
video, like this one for example, you're probably not
all watching it from the same server.
It gets distributed all around the world.
TED HAMILTON: So there is the original, which
you will have uploaded.
Or I guess by the time you are watching this,
have already uploaded.
Then this gets, what do you call it?
Cached in different locations, so that when you make a
request for a video, it doesn't need to travel all the
way from London over to California and say OK, send me
back all of these bytes way back here.
BRADY HARAN: So with multiple copies of the video all around
the world, counting the views starts to get a little bit
more complicated.
TED HAMILTON: Here's you at your computer
watching the video.
If you make a request to this server, this server is going
to give you the video, right?
And at the same time, this server is going to write a
little message to a log.
It's just one line in a log.
Every once in awhile, we collect all of these logs.
So we'll ship this thing in from central Europe, or
whatever into the central log collection area, aggregate
them all together, and then go through and count them up.
BRADY HARAN: Well OK, that seems simple enough, but it
doesn't explain why the view counter freezes.
TED HAMILTON: Views, as mentioned, are a currency.
When you have a video with a very small amount of views,
then you don't need to be too careful about
what that view was.
However, once it gets to be above 300 and beyond, this
currency we really need to verify and make sure that the
number is what it purports to be.
So this means that we have to go through a statistical
verification process, and that statistical verification
process actually takes some time.
And thus we go from incrementing one by one to
then saying, OK, now we're incrementing in batch, and all
of these views that have been added on have been verified by
YouTube to be real views.
We are preventing things like bots to go in and add a bunch
of views to a video.
Or we are preventing something that may have perhaps misled
someone into watching a video.
Say you had a title that was completely misleading, and a
thumbnail that was completely misleading, and people
actually went on there and just viewed for a few seconds,
and then left.
If you see that enough times, it a fair enough indicator
that something was wrong there, so that we might not
authorize all of those to be legitimate views.
BRADY HARAN: All right, then.
They're verifying the numbers.
They're checking everything.
I guess we probably could have guessed that.
But why 301?
TED HAMILTON: I was not there when the decision was made,
but at some point the decision was made that we need to draw
a line between what is innocuous and the database can
handle, and what is all of a sudden serious business.
The proportion was calculated to be at about 300, that this
is the portion that we need to take care of.
But the formula that we use to arrive at 300, I don't know if
anyone actually knows that.
BRADY HARAN: Well, OK.
They drew a line in the sand.
It was kind of arbitrary.
They wanted to differentiate between people just sharing
their home movies and the videos that are more popular,
the ones that are a bit more serious.
The ones that need scrutiny.
But that was 300.
The view counter freezes at 301.
What's going on here?
Is there a reason?
TED HAMILTON: Yeah, there is a reason.
And the reason was the number 300 was chosen.
And when someone's writing code, they need to put the
logic in the code that says where you should stop, or
where you should, if one condition is true,
you go to the left.
And the other condition is true, you go to the right.
Now, this condition can be written like this.
If the view count is less than 300, then go ahead and add one
to the view count.
Otherwise, go to x where x is our much more complicated view
count pipeline.
However, what actually got written was not this, but if
view count is less than or equal to 300, then increment
the view count.
So what this means is if the view count is at 300, this
says is the view count less than or equal to 300?
Yes, it is.
Let me add one.
So then you end up at 301.
BRADY HARAN: Let me recap what's going on here.
The code which is controlling where this view counter
freezes contains a less than or equal to sign.
So that means when a new early view comes along, it's checked
against the code.
Say the overall view count on the database is 299.
OK, then.
We'll let another one on.
Here comes another view.
Now the view count is 300.
That isn't less than 300, but it is equal to 300.
So the code lets another view jump onto the total.
Now we're at 301, and when another view comes along, it's
not less than 300, but it's also not equal to 300 anymore,
and the door is shut.
There are going to be no more views added to the publicly
visible count until YouTube have done their checks.
And that will take half a day to a day.
Then of course, all the extra views that have been counted
in the interim all pile onto the total.
Nothing's missed.
At least that's what I'm told.
TED HAMILTON: Yeah, so whoever wrote this code probably did
not realize the magnitude of what they were doing.
View counts have been around since the beginning of
YouTube, and who was to know what YouTube would become.
So yeah, that was actually a rather monumental second of
time in San Bruno, California, when a coder decided to write
that logic in.
It is now one of the idiosyncrasies of YouTube.
BRADY HARAN: Now, I can hear some of you screaming at your
computer screens.
The view count doesn't stop at 301.
Sometimes it stops at 302, or 305, or 310.
What's going on there?
There's an explanation for that, too, and that comes back
to how I was saying the videos are shared around servers all
across the world.
So here's what's going on there.
Views are coming in from the logs at the different videos,
the different places around the world.
And they're coming to this central database.
And we know the door's going to be shut at 301, we just
explained that a minute ago.
But what happens if views are coming in at the same time?
Someone watched it in Africa at the exact same time someone
watched in Europe.
Now we've got multiple views coming in.
Checking if they're allowed to join the count, yes they are.
It's less than or equal to 300.
So they all pile on at the same time.
Now when a new view comes along, sorry,
we're closed for business.
But because of that simultaneous update, a few
extra views were able to sneak on.
TED HAMILTON: We get asked about it all the time.
I wouldn't say that it causes angst, but it's certainly, I
would classify it more as an annoyance.
You can go and see a very popular video, and you look
and you'll see that it has 2,000 likes and 300 views.
That's a little bit interesting.
The issue there is that we don't put the likes through
the same rigor, same rigorous process.
And likes are far fewer in magnitude, so our systems can
handle them more easily.
But the views do freeze, and it can result in some awkward
situations.
But that actually results in terrific videos like this, so.
BRADY HARAN: I did speak to Ted for maybe 45, 50 minutes
and recorded it all.
I've got loads of footage, a lot more detail, including a
bit more about what constitutes a view.
And I know some of you will want to see it.
I haven't had time to edit it all just yet, but stay tuned
because I'll be uploading that to
Numberphile in the near future.
And for those of you who don't like these ones that are a bit
more about computers and the internet, I'm sorry.
Numberphile's always unpredictable, and I promise
next time it might be something
you enjoy a bit more.
MATT PARKER: How many arrows do you want?
So the next one, let's say we did 3 to the power of, to the
power of, oh, arrow, arrow, arrow, or whatever you
want to call this.
3.
Will that--
浏览更多相关视频
Networking for GenAI Training and Inference Clusters | Jongsoo Park & Petr Lapukhov
Psychology of Computing: Crash Course Computer Science #38
Case Interview: Essential Tips and Tricks (Part 12 of 12) | caseinterview
Software Engineering: Crash Course Computer Science #16
Lecture 1.1 — Why do we need machine learning — [ Deep Learning | Geoffrey Hinton | UofT ]
Photography and Materiality: John Opera in dialogue with Karen Irvine
5.0 / 5 (0 votes)