It was observed on English Language Learners beta; but I think is applicable for other SE websites too.

While answering(and after answering) this question on ELL SE; I noticed that the number of views on the question were 1. I refreshed(Ctrl + F5) the page, and it still was 1. I then moved back to the home page; and once more it was just 1 view.

Img 2

How can a question with 2 replies be stuck at just one view?

P.S.: You can also notice that the view count hasn't changed from 1 even after 10 minutes from the first reply:

Img 3

  • 15
    Caching, it's always caching... – yannis Mar 18 '13 at 8:07
  • @Yannis Even after half an hour? – hjpotter92 Mar 18 '13 at 8:09
  • Also, THIS question has already struck a count of 5 views in 3 minutes. – hjpotter92 Mar 18 '13 at 8:10
  • 1
    Yes, but this question is on MSO, not on a beta site. Betas don't get much traffic, so longer TTLs make sense. Only a SE dev can answer this authoritatively, but... it's caching ;) – yannis Mar 18 '13 at 8:14
  • @BackinaFlash - Yep. I have observed the same in Sports.SE. – hims056 Mar 18 '13 at 8:15
  • This is server cache, F5 or clearing browser cache won't help. Anyway my guess is that the cache is updated in "bulks", i.e. not after every single view but rather after 5, 10, 15 etc. This explains the behavior. – Shadow Wizard is Ear For You Mar 18 '13 at 8:16
  • 1
    hmm. It changed to 4 views after 40 minutes. – hjpotter92 Mar 18 '13 at 8:19
  • @Yannis Do you really think caching a question with only 1 view makes sense? – pvorb Mar 18 '13 at 8:30
  • @pvorb the views are cached, not the question. Instead of going to the live table each time the code is going to a cache and that cache updates every X minutes, maybe depending on other factors as well. – Shadow Wizard is Ear For You Mar 18 '13 at 8:38
  • @ShaWizDowArd This might be the case, but isn't caching usually only useful when done for more frequently used objects? (But I'm not a SE dev, so I can't tell) – pvorb Mar 18 '13 at 8:44
  • 2
    @pvorb: The views of 20ish questions are fetched every time someone opens the main page – Manishearth Mar 18 '13 at 8:46
  • 1
    @pvorb the point behind caching is avoiding expansive trips to database; on Stack Exchange virtually everything is cached otherwise their database would work slower than a tied up turtle. :) – Shadow Wizard is Ear For You Mar 18 '13 at 8:47
  • @Manishearth You are right. I didn't realize that. – pvorb Mar 18 '13 at 8:47
  • 1
    While not even google seems to know what the speed of a tied up turtle is I must assume it is not very fast. This issue seems to be an edge case of speed over functionality. – Travis J Mar 18 '13 at 9:16
  • 3
    @TravisJ An African or European tied-up turtle? – Andrew Barber Mar 18 '13 at 11:46

You must log in to answer this question.

Browse other questions tagged .