ISSUE-12: Determine appropriate size limit for beacon data based on current usage patterns

beacon-size-limit

Determine appropriate size limit for beacon data based on current usage patterns

State:
CLOSED
Product:
Beacon
Raised by:
Jatinder Mann
Opened on:
2014-03-05
Description:
Determine appropriate size limit for beacon data based on current usage patterns to help us determine what the right limit should be for beacon data transmissions and whether we should set a limit on number of beacons per page or rate at which beacons are transmitted. Ilya, you had mentioned that you were going to look at Google Analytics data to see what the common analytics package sizes are? That data will go a long way in helping us determine an appropriate limit.
Related Actions Items:
Related emails:
  1. Re: {minutes} 2014-04-26 Web Performance Working Group: Resource Priorities, HRT2, Beacon, etc. (from arvind@google.com on 2014-04-05)
  2. {minutes} 2014-04-26 Web Performance Working Group: Resource Priorities, HRT2, Beacon, etc. (from plh@w3.org on 2014-03-26)
  3. Re: [agenda] Web Performance WG Teleconference #129 Agenda 2014-03-26 (from plh@w3.org on 2014-03-26)
  4. ISSUE-12 (beacon-size-limit): Determine appropriate size limit for beacon data based on current usage patterns [Beacon] (from sysbot+tracker@w3.org on 2014-03-05)

Related notes:

We had reached consensus to return an error synchronously if size/queue limits are exceeded and not specify an explicit size limit.
See this thread for discussion:
http://lists.w3.org/Archives/Public/public-web-perf/2013Dec/0062.html

Arvind Jain, 5 Apr 2014, 19:51:53

Display change log ATOM feed


Yoav Weiss <yoavweiss@google.com>, Todd Reifsteck <toddreif@microsoft.com>, Ilya Grigorik <igrigorik@google.com>, Chairs, Xiaoqian Wu <xiaoqian@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $