What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 133 Stack Exchange communities.

Two close votes and only one person has viewed the question?

screenshot

How did this happen?

share|improve this question
13  
Freehand drop shadows? What were you thinking? –  balpha Apr 17 '10 at 5:53
1  
@balpha: I had to make up for the fact that I didn't know about freehand circles before.. –  Billy ONeal Apr 17 '10 at 6:34
4  
I literally cracked up when I noticed the drop shadows! –  Earlz Apr 17 '10 at 7:35
2  
+1 for freehand drop shadows, even though they were visibly added after the circles :D –  Pëkka Apr 17 '10 at 9:03
    
@Pekka: How else would you add them? –  Billy ONeal Apr 18 '10 at 3:07
    
@Billy by drawing the shadows first, and the circles on top of them. –  Pëkka Apr 18 '10 at 8:28
    
@Earlz: Haha, me too. And I very rarely actually laugh at stuff I see on the internet. –  Lightness Races in Orbit Jun 23 '11 at 23:35
    
+1 cause I've noticed this, and also for the pluralization. –  Andrew Grimm Dec 28 '11 at 1:26

2 Answers 2

up vote 5 down vote accepted

Likely due to caching. Close-vote counts are probably not cached, since that information is extremely important and prone to change rapidly. This, however, is not the case with views which could be cached and updated in longer periods.

share|improve this answer
4  
Yet another reason why there should be a list somewhere of everything that is cached on the site :) –  Earlz Apr 17 '10 at 7:35

Since other questions are being pointed here as dupes, I'll update this question. From a technical standpoint, this was a separate issue than we have currently with caching. Since this question, we greatly changed how ViewCount is stored/processed/updated.

Starting last night new questions are cached significantly less than old questions, the current rules are:

  • A question under 10 minutes old will only cache it's view count for 30 seconds
  • A question over 10 minutes old will cache for 5 minutes (we have a lot of view counts to cache...)

This should improve the UI since a new question is where this caching is more apparent/strange looking.

Keep in mind this doesn't solve the issue, it just improves it. It would cause mass chaos to update the database on every view hit, so we collect a few before doing a batch update on each web server (30 on most sites, 300 on SO). It's still possible (mainly at slower times of the day) to see some mis-match like the above screen shot, due to those close voters having views in a buffer that hasn't got enough views to flush yet for example, or just the 30 second caching itself.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .