Last modified: 2007-04-03 20:13:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 9488 - optimize js/css output
optimize js/css output
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-04-03 20:06 UTC by Carl Fürstenberg
Modified: 2007-04-03 20:13 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Carl Fürstenberg 2007-04-03 20:06:33 UTC
The question I have is: Would the code-size reduction by using something similar
to GzOutput, on mainly js/css, result in a net gain of performance/bandwidth
throughput? If so I propose to implement/use the package linked.
Comment 1 Rob Church 2007-04-03 20:08:41 UTC
We already use output compression, where supported by the browser and web server.
Comment 2 Carl Fürstenberg 2007-04-03 20:10:22 UTC
I know you have compression, I was thinking more to remove comments and
whitespaces and such things also.
Comment 3 Rob Church 2007-04-03 20:13:15 UTC
(See previous discussion on wikitech-l)

Note You need to log in before you can comment on or make changes to this bug.