[wp-trac] [WordPress Trac] #21646: Bump memory limit from 32MB

[WordPress Trac]

#21646: Bump memory limit from 32MB
-------------------------+------------------
 Reporter:  nacin        |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  3.5
Component:  Performance  |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+------------------
Description changed by nacin:

Old description:

> On some shared hosts and servers, WordPress runs perilously close to 32MB
> in the dashboard, especially with a number of plugins included. It's time
> to bump. I am thinking 40MB as a good, relatively round number.
>
> In the near future (once our minimum PHP version is 5.3, and possibly
> earlier for those already on 5.3), we can look into autoloading of all of
> our classes. That should take down our memory a bit. (kurtpayne has
> looked and it's not much, mainly because so many of them are used on most
> pages.)
>
> Note that increasing the memory limit does not actually result in 8 more
> megabytes of memory being used. WordPress won't start eating up that
> memory — just that PHP allows the script to use up to 40MB. Otherwise,
> hitting 32 would give a fatal error.
>
> We also should ''not'' take this as a license to further increase the
> side of the WordPress codebase, which has crept up at a pretty steady
> pace over the years. The only objective is to avoid fatal errors on
> individual.

New description:

 On some shared hosts and servers, WordPress runs perilously close to 32MB
 in the dashboard, especially with a number of plugins included. It's time
 to bump. I am thinking 40MB as a good, relatively round number.

 In the near future (once our minimum PHP version is 5.3, and possibly
 earlier for those already on 5.3), we can look into autoloading of all of
 our classes. That should take down our memory a bit. (kurtpayne has looked
 and it's not much, mainly because so many of them are used on most pages.)

 Note that increasing the memory limit does not actually result in 8 more
 megabytes of memory being used. WordPress won't start eating up that
 memory — just that PHP allows the script to use up to 40MB. Otherwise,
 hitting 32 would give a fatal error.

 We also should ''not'' take this as a license to further increase the side
 of the WordPress codebase, which has crept up at a pretty steady pace over
 the years. The only objective is to avoid fatal errors on individual
 sites.

--

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/21646#comment:1>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software