Tickets :: Comment on [#13761] Memory usage issues when IMAP sequence range is far apart

* Your Email Address
* Spam protection	Enter the letters below: .__..__ .__ .___ __ \| \|[__)[ __[__ / ` \|__\[__)[_./\| \__.
Comment	>> Ive had an issue with one user where the range was over 1m between >> min & max and the max memory had to be over 256Mb > > They have 1 million messages in their mailbox? The expectation for a > mailbox that large MUST be that it is going to take a lot of memory. > >> Using SplFixedArray the max memory limit can be reduced to about half >> but there are big issues elsewhere as the Spl does not have all the >> sort functions that a standard array has. > > That's exactly the issue. You can optimize for memory, but then you > lose speed. > > Since most people have mailboxes less than 1 million messages, the > obvious choice is to optimize this scenario. > > Not to mention that there is very little you can do when working with > a list of messages that may NOT be in sequential order. i.e. a 1 > million element UID list where every other UID is skipped. > > Doing things like binary packing and in-line compression are possible > options, but these are complicated additions and not something that I > am going to tackle unless someone is paying me. > >> Another problem is found on line 170, would it not be prudant to >> unset each array key as it is populated into the _add array, that way >> the memory should not balloon (not sure if PHP optimises for this >> anyway). > > This is irrelevant for PHP memory handling. There is no direct > access to PHP memory/garbage collection that's going to make a > difference in this situation. >
Attachment
Watch this ticket

Saved Queries