[wp-trac] Re: [WordPress Trac] #3141: explicit memory check before starting install

WordPress Trac wp-trac at lists.automattic.com
Sun Jan 27 19:30:58 GMT 2008

#3141: explicit memory check before starting install
 Reporter:  looksaus                 |        Owner:     
     Type:  defect                   |       Status:  new
 Priority:  normal                   |    Milestone:  2.5
Component:  Administration           |      Version:  2.1
 Severity:  normal                   |   Resolution:     
 Keywords:  has-patch commit tested  |  
Comment (by darkdragon):

 It isn't just install, it is actual running of WordPress that does not
 fall into 8MB of memory. I believe Godaddy also allows for this.

 So I mean, at least two shared hosts, that are popular do this. What
 disadvantage is there?

 Not including it: Everyone that could have benefited now has to go to
 Including it: Those that can't increase memory, won't, so it is optimized
 for them and they won't feel the burn. Those that can, will have a minor
 decrease in performance, but will be able to not need support.

 It is the similar method used in openads, so while I'm not exactly sure
 what their code looks like, I know at least that the algorithm is similar.

Ticket URL: <http://trac.wordpress.org/ticket/3141#comment:40>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list