| Re: [cross-project-issues-dev] p2 download statistics broken or biased? |
|
Hi again, Here are some final observations about download stats. ·
Helios stats are found under /stats/releases/helios in the portal ·
The number of stat counters in Helios has gone down from 84 in Helios to 23 in SR1, then 27 in SR2: ·
My TM project doesn’t count stats in Helios SR1 or SR2 since we add stats only to “release” sites but Helios has been aggregated from “interim” sites
o
I have since changed our contribution to reference the “release” site rather than interim, but I don’t expect a re-aggregation to be realistic?
·
The ID’s for WTP/WST stat counters are not exactly consistent in SR2, though they were in SR1: <property name='download.stats' value='org.eclipse.wst.web_ui.feature'/> <property name='download.stats' value='org.eclipse.wst.xml_ui.feature'/> <property name='download.stats' value='org.eclipse.wst.jsdt.feature'/> <property name='download.stats' value='org.eclipse.tptp.wtp.feature_helios_sr2'/> ·
The top 6 downloads from Helios in terms of stats so far are: I still find the statistics highly suspicious, especially because daily stats show downloads of “Helios SR0” content up until today … which is unlikely correct since everyone should be getting SR1 by now I’d
assume. As I mentioned, I have fixed the stat contribution for my TM project, re-aggregating this somehow would be interesting for us but it’s not a must have. Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin Digging a little deeper and looking at stats by day and by country, I see that 1. By country distribution is as expected, with a clear maximum in the US 2. By day distribution shows many “_tm320” downloads (which would indicate Helios non-SR1)of the examples up until today. I have no explanation for this, since on our TM project site we ONLY distribute the _tm321 bits, and Helios never had the “examples” bits. Does this ring a bell for anyone? -
Could these “_tm320” downloads come from any mirrors that I do not know? -
Could these be generated by clients updating from 320 to 321, even if only 321 bits are being downloaded? -
Could it be a bug in the p2 code or in the stats counter at eclipse.org? Ideas welcome… Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin Hi all, Preparing our TM Helios SR2 release, I was also testing our p2 download stats. Along those lines I retrieved the existing stats for Helios and Helios SR1. What I see is making me wonder whether there’s any problem collecting the stats, or any automated download agents leading to broken results: ·
Some of our “esoteric” offerings like examples or unittests get very low numbers as ZIP downloads but very high numbers from the p2 repo.
o
These offerings are NOT available from Helios, but only our project site, and relatively hard to get to. ·
Between Helios Release and SR1, our ZIP downloads are approx. the same number, but SR1 update site stats are less than half of the Release? ·
Our SDK offering should “include” the runtime offering but yet the runtime stats are lower than the SDK stats ?!? It’s completely possible and likely that I’ve been doing something wrong on the stats preparation, retrieval or data interpretation… but I’m wondering if anybody else is seeing the same? FWIW, I’m relatively certain that the results are
not tainted by Milestone downloads, these are for the release only. FYI, full stats with more data are at
http://dev.eclipse.org/mhonarc/lists/tm-dev/msg00015.html Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 |