[wp-trac] [WordPress Trac] #14889: Memory Comparison Broken / WordPress Memory Limit

[WordPress Trac]

#14889: Memory Comparison Broken / WordPress Memory Limit
-----------------------------------------------+---------------------------
 Reporter:  hakre                              |       Owner:
     Type:  defect (bug)                       |      Status:  new
 Priority:  normal                             |   Milestone:  Future
Component:  General                            |  Release
 Severity:  normal                             |     Version:  3.0
 Keywords:  has-patch 3.2-early needs-testing  |  Resolution:
-----------------------------------------------+---------------------------

Comment (by hakre):

 wow, much news ;)

 @aaroncampbell (et al) array_search is pretty costly (that's known, just
 saying), I was looking into pow as well, probably searching in a string
 ("BKMG") is faster (and/or with array_search to set $strict param to
 true).

 Sparing the pow by using precalculated values is somehow reasonable as
 we're lucky to have a function with local scope already that get's dropped
 after being used (for the local vars especially like $map).

 @chrisbliss thanks a lot for the quick support and directing the tests. I
 really appreceate your input and the way you're taking care. I really have
 missed the -1 case and I think that's more important here in this issue.
 Otherwise we might have solved the "m" vs. "g" while still not parsing the
 ini setting to the full range of options (for which this ticket was
 opened!: the _full_ range of options to deal with properly as ini settings
 are user input we need to deal with properly within widespread
 applications).

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