W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2013

Re: [Beacon] spec feedback + few suggestions

From: Ilya Grigorik <igrigorik@google.com>
Date: Tue, 19 Nov 2013 17:08:27 -0800
Message-ID: <CADXXVKpxU7zEqOjn-4c=JZDjhyXEFH6=tkYVL1g_yj+G00HqVQ@mail.gmail.com>
To: Jatinder Mann <jmann@microsoft.com>
Cc: "Austin, Daniel" <daaustin@paypal.com>, Jonas Sicking <jonas@sicking.cc>, Chase Douglas <chase@newrelic.com>, public-web-perf <public-web-perf@w3.org>
On Wed, Nov 6, 2013 at 4:11 PM, Jatinder Mann <jmann@microsoft.com> wrote:

> Iíve also opened Action 111: Determine appropriate size limit for beacon
> data based on current usage patterns [2] 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.


After some back and forth with the GA team... "10KB per beacon limit is
sufficient for current GA needs". Unfortunately, the GA team has asked me
to not disclose the exact distribution, but based on the data I've seen,
10KB is in the right ballpark: it covers current use cases and provides
some margin for growth. That said, values below 10KB will begin to pose
problems pretty quickly.. So, it may be worth considering 10KB as a good
floor value.
Received on Wednesday, 20 November 2013 01:09:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:37 UTC