The mysteries of FA stats
10 years ago
General
According to FA, the first chapter of "Going Concerns" has 452 views; none of the following chapters have more than 64. But some middle chapters have fewer views than some later chapters.
(For comparison, over on SoFurry, the first chapter only has 105 views, but following chapters have roughly comparable views to FA.)
(For comparison, over on SoFurry, the first chapter only has 105 views, but following chapters have roughly comparable views to FA.)
FA+

(You may have just also provided a data point for a discussion between another FWG member and myself from the other day...)
'multi-page' stories, several darn huuuge.
I'm going an extra mile too. I cut a script that I run on a daily basis. It captures all the stats pages,
then peels out the #s for all subs posted in two accounts (over 600 subs). Then drops the data into a
spreadsheet so I can make sense out of what's being read. I'm tracking all subs on a day-to-day
basis.
Splendidly geeky thing to do. :- ) Debatable how useful.
Almost every story shows a real spread in view counts from the first sub to the last. Which puzzled the
snot out of me at first. The pattern ought to be, high counts on the first pages, then dropping down
smoothly as some readers decide to stop reading at various points.
Nope: Not what we get. Spiky numbers, not smooth. Is FA's page counter code borked, and is it failing
to capture views? Dunno.
Alternate theory: The way FA works, people will trip over any given sub in a multi-sub doc almost at
random, and may not read further. Tick up a random view count. Or, they may get curious, then go
back to page one and start reading. Then some will stop a few pages in.
Result: A pattern of view counts that only poorly reflects how many people read the whole puppy. Can
think of ways to improve on this, but moah script won't help. Need to pry the hood off FA's codebase
and do some tinkering.
Lemme lift up... <Creak!> Wow, who'd have thought you could cram so many hamsters on wheels into
a server? :- )
Your alternate theory about tripping over given pieces of a multi-submission work is about the same as my drive-by theory: somebody sees it on the front page and clicks, especially if you've gone to the trouble to make a pretty icon and everything, but doesn't necessarily follow up by going back to the first chapter.
I wouldn't be surprised if FA's view counter is a bit flaky, of course, although in my experience page counters are sadly more likely to overestimate than underestimate...
how my work's doing. The data is current, not historical, can't really be analyzed
(since stuck on an FA page).
Fortunately, stats-scan2 was a dead-simple program to write; not-a-lot-of-work,
in other words. Almost certain I'm the only one on FA who's doing this.
Since I've got historical data in paw, I've been able to see several view count 'glitches,'
as a range of sub numbers suddenly go weird. Called in a TT a couple of times, much
to the confusion of some poor Admin. :- )
'S probable that FA's view counter code is quite robust. How to record views and hits is the
most well-solved software problem on the Internet.
But: That code relies on a raft of DBs and data structures and temp files, all sitting
on a busy server, and *not* as robust. If those get interfered with our view counts get
temporarily borked. And a sysadmin snarls like rabid to try and fix things.
C'mon you hamsters, back on those wheels. Don't make me use the whip. <Ka-pish!>
<Squeal!!>
Oh crud, they're putting on tiny handcuffs and ball gags. I think they're starting to like it. :- )