You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wrote a simple bash/curl script (direct call to the pixel) to simulate traffic and noticed once load is placed on the Hummingbird server the reported pageviews per second is approximately double the corresponding y-axis value (or y-axis values are half the number of page views, which ever you prefer). For example: If Hummingbird is reporting 30 pageviews/second the average y-axis value is somewhere around 14-15. (See linked photo: http://i103.photobucket.com/albums/m145/xtmesisx/Screenshot2011-07-21at30218PM.png)
I suspect that the logic generating the y-axis values is off (display issue), but I'm not sure what to change. I've been fiddling with it for a few hours now and haven't figured it out yet.
Does anyone have thoughts on the matter?
The text was updated successfully, but these errors were encountered:
So I believe I found the problem. The variable "averageOver" (Line 27) is set to 0.5 by default. I'm not 100% sure what it does, but it looks like the "averageOver" is passed into the function drawLogPath() when it multiplied by "average" on line 49. To fix my issue I simply set "averageOver" to 1.0.
If anybody could explain further and/or verify I'm correct/on the right path it would be greatly appreciated. For now pageviews per second the the y-axises seem to match up (tested again with traffic simulation script).
I wrote a simple bash/curl script (direct call to the pixel) to simulate traffic and noticed once load is placed on the Hummingbird server the reported pageviews per second is approximately double the corresponding y-axis value (or y-axis values are half the number of page views, which ever you prefer). For example: If Hummingbird is reporting 30 pageviews/second the average y-axis value is somewhere around 14-15. (See linked photo: http://i103.photobucket.com/albums/m145/xtmesisx/Screenshot2011-07-21at30218PM.png)
I suspect that the logic generating the y-axis values is off (display issue), but I'm not sure what to change. I've been fiddling with it for a few hours now and haven't figured it out yet.
Does anyone have thoughts on the matter?
The text was updated successfully, but these errors were encountered: