This is related to the 'number of times your profile is visited by others'.
How exactly does it work? For example, in my profile page, profile view count is 171.
As far as I know, the profile counter increases when any new user visits your profile. The Stack Engine might be storing some data related to the user who visited your profile once and checks it next time if the user visits. If it's a new user your profile counter increases else remains the same. This is just a thought from my side that how it would be working, exactly Moderators might give a better idea.
To note, I am not a Stack Exchange developer nor am I associated with them. As such, this is an unofficial response. I was just very curious and am a huge fan of the ASP.NET MVC framework. These are my findings.
I believe it is caching... it is always caching.
What is it caching? It is caching something Stack Exchange has termed QuerySets which are pretty much stored sql execution plans which match to a query, a userid, and an ip address (there are a few other params). This information is dated, I am pretty sure the code is a cached version. But really, it is from 2012ish.
The execution plans are cached in
The QuerySet is created the first time a sql execution plan is created from one IP address requesting a page, otherwise the QuerySet is cached, in which case the revision is updated. The cache window is 15 minutes, and inside of this window, no new views are counted. Every time the QuerySet is fetched it will reset the window.
If the window has expired, then it will increase the count - note
The call to isNewView is checking to see if the current QuerySet which is saved is relevant for the page based on the current time window.
This is how it used to be, I am fairly certain that it has changed. When content changed, the
Now, back to the exact scenario explained in the bounty for this question by LowerClassOverflowian. How can he have 1000 views in 3 months? Personally I think 5k rep in 3 months is pretty impressive, and the views relate to people who have benefited from the content produced by this user.
This was the best I could do from the outside looking in.