New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase beacon frequency until there's enough data, then decrease it. #937

Closed
GoogleCodeExporter opened this Issue Apr 6, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Apr 6, 2015

PageSpeed beaconing through v1.7 would add beacons to pages at a regular 
interval (5s by default).  High-traffic pages would not get beaconed on most 
page views, and low-traffic pages would tend to get enough instrumentation to 
be able to make optimization decisions.

We can safely beacon even less often (say every 10min) when beacon results are 
stable over time.  We should turn up beacon frequency when conditions change.

Original issue reported on code.google.com by jmaes...@google.com on 1 May 2014 at 6:13

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

(Stumbled on this interval feature and currently use it to cache non-beaconed 
pages in Varnish)

Maybe Min and Max beacon intervals could be config parameters ?

Webmasters could then individually finetune beaconing depending on the nature 
of  content and trafic.

Original comment by p.co...@gmail.com on 12 Jun 2014 at 9:31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment