I’m currently stress testing a LiteSpeed webserver for import in 18.104.22.168 because the export once again is running out of memory somehow.
768M memory_limit and on running an export profile, Magento dies with a malloc error indicating that there’s some internal problem with a 128M memory limit being exceeded. DESPITE EVERYTHING TELLING YOU IT’S 768M LOCAL AND SYSTEM.
Here’s the resulting digital spew:
Fatal error: Out of memory (allocated 134479872) (tried to allocate 4096 bytes) in /home/x/public_html/app/code/core/Mage/Eav/Model/Entity/Attribute/Source/Table.php on line 62
Fatal error: Out of memory (allocated 134742016) (tried to allocate 24 bytes) in /home/x/public_html/lib/Zend/Db/Select.php on line 924
Fatal error: Out of memory (allocated 133431296) (tried to allocate 5541 bytes) in /home/x/public_html/lib/Zend/Db/Statement/Pdo.php on line 228
Fatal error: Out of memory (allocated 133169152) (tried to allocate 24 bytes) in /home/x/public_html/lib/Zend/Db/Select.php on line 924
Having been through four different Linux installs with Magento, with different iterations of Apache/Mod_php5, Apache/FastCGI, LiteSpeed/lsphp5, you will find on high volume production sites, that there’s always something dropping a wrench in the transmission. You get one system tuned up to where it works, and decide you need more performance, only to bring yet another fresh set of problems. Apache/FastCGI seems to work the best with the least resource hogging (LiteSpeed = fast with issues), but you’ll need some nice heavy iron to run it with any speed. Thankfully, exports are not Magento’s main function, or I’d have put a bullet through its brain a long time ago.