3.0 package size will cause memory limit problems
|Reported by:||nacin||Owned by:||nacin|
|Priority:||highest omg bbq||Milestone:||3.0|
|Cc:||paulgregory, dre@…, chip@…, pavelevap@…|
I've seen multiple reports that the 3.0 download is too much for the 32MB limit. I can also reproduce this on a reputable shared host.
We do increase to 256MB once the package is downloaded, to unzip the file. But that doesn't help here -- download_url is struggling. We also can't add anything to update-core of course, as we haven't even downloaded the package yet.
After talking this over with MarkJaquith and westi, this is fixed in , where we will give anyone with the manage_options capability a 256MB memory limit in wp-admin.
That said, this will still blow up on many hosts and configurations with the default WP memory limit (that'd be 32MB) when upgrading from 2.9.2 to 3.0. Telling everyone who experiences the error to add a constant is a bad idea from basically every standpoint (starting with PR) and will severely hurt 3.0 adoption.
So, we need to prune the 3.0 download package. For reference, it is currently ~3.2MB, while 2.9 was only 2.5MB, 2.8 was 2.4MB, and 2.7 was 1.9MB. Obviously, a lot of this is due to the merge.
I can't come up with many things we can remove, but I can start with two folders of items: CodePress (I was planning to do this first-thing in 3.1 anyway), and the theme-compat folder (fall back to Kubrick, and if it doesn't exist, tough luck).
If that's not enough to get us under the bar, we'll need to get more creative. As a start, image gradients in wp admin that can become CSS3 (we just did this with the admin headers), and other images that can be compressed and/or become sprites. I have other crazy ideas I'll keep to myself for now.
Change History (54)
- Resolution fixed deleted
- Status changed from closed to reopened
- Resolution set to fixed
- Status changed from reopened to closed