Re: FW: Help needed in benchmarking memory patch

Hi Andi, I appreciated to see this code which I must still study. Already a small remark it is that the system call mremap() is not portable it is available only on Linux. Then the size of the segments must always "be paginated" - normally your code is good on this level. I think that a concept of kernel-memory and user-memory can be very interesting to study, especially in threads environments - that I use. I would continue to look at your code but now I will sleep (04:26 pm)! mv- ----- Original Message ----- From: "Andi Gutmans" <andi@zend.com> To: "'Andi Gutmans'" <andi@zend.com>; <internals@lists.php.net> Sent: Monday, July 10, 2006 5:57 PM Subject: RE: [PHP-DEV] FW: Help needed in benchmarking memory patch

No help??? Come on guys. I'm sure some of you can spare a few idle cycles :)

-----Original Message----- From: Andi Gutmans [mailto:andi@zend.com] Sent: Friday, July 07, 2006 8:38 PM To: internals@lists.php.net Subject: [PHP-DEV] FW: Help needed in benchmarking memory patch Sending 3rd time this time without the attachment. You can get the diff at http://gutmans.org/alloc.zip -----Original Message----- From: Andi Gutmans [mailto:andi@zend.com] Sent: Thursday, July 06, 2006 11:06 PM To: 'internals@lists.php.net' Subject: Help needed in benchmarking memory patch Hi all, Attached is a patch we've been working on to improve the memory management of PHP. This patch's main advantage is reducing the memory footprint of PHP, and therefore allowing it to scale better. Although at low concurrencies the change seems to be negligble, while testing at higher concurrencies we saw significant improvement with this patch, mainly due to lower memory usage. We would very much appreciate if people here tested this patch and send in their results. It would help us understand if others are getting consistent results with ours, and also see whether there are any additional improvements we should make. This patch should apply cleanly to the PHP 5.2 CVS tree. There's not much tuning that needs to be done. It uses malloc() to allocate large memory blocks. You can control the size of these blocks by setting the ZEND_MM_SEG_SIZE environment variable before starting Apache/PHP. You may use K or M to play around with the block size. The default we are using is 256KB which seems to be a good balance. Any feedback would be appreciated! Andi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php