Opened 7 years ago

Closed 2 years ago

#7517 closed defect (wontfix)

Devise and deploy the canonical median web page

Reported by: arma Owned by:
Priority: Medium Milestone:
Component: Archived/Torperf Version:
Severity: Keywords:
Cc: ln5, karsten, wrs Actual Points:
Parent ID: #7168 Points:
Reviewer: Sponsor:

Description

Drew Dean and many others tell us that the typical web page these days is 320KBytes with multiple components.

Great -- why do they say this? How many is 'multiple'?

Once we *do* have some answer, what's the rate of change over time of this "average" web page? (I.e., will anything we pick now be substantially wrong in six months, or will it last us for a few years?)

We should take some guesses, based on whatever data we think appropriate, and set up this median web page. Then we can use it as the target for the #7516 scripts once they're online.

Child Tickets

Change History (5)

comment:1 Changed 7 years ago by ln5

Cc: ln5 added

comment:2 Changed 7 years ago by karsten

Cc: karsten added

comment:3 Changed 7 years ago by arma

Cc: wrs added

comment:4 Changed 7 years ago by wrs

This might be a lead for figuring out a way to define "typical"
http://www.optimizationweek.com/reviews/average-web-page/

The 2012 Data point claims that average pages today have 100 objects and 1.1 Megs of data. Unclear how reliable that data is.

comment:5 Changed 2 years ago by karsten

Resolution: wontfix
Status: newclosed

We officially switched from Torperf to OnionPerf for Tor performance measurements. We don't need these tickets anymore and will use OnionPerf's issue tracker for OnionPerf-related issues. Closing them all as wontfix.

Note: See TracTickets for help on using tickets.