How could it not? If the only pages that require more than 128 megs are on your back end and you set the memory limit to 256 for them and 128 for the rest of the site (or possibly lower), and tune your apache settings to expect no more than 128 rather than boosting memory for the entire site and configuring apache to expect 256 megs, you couldn't *not* improve performance of your webserver. I'm not sure what value benchmarks would offer aside from the obvious, yeah?
PHP only uses what it needs. If you set the maximum to 1GB globally, and drupal takes 128mb, 1GB will not be allocated. The only way for this to work like you're hoping (increase server capacity) would be to run high memory PHP pages from the command line.
Comments
Comment #1
caseyc commented@mikeytown2, what specifically would you like regarding benchmarks?
Comment #2
caseyc commentedComment #3
mikeytown2 commentedShowing that this helps with memory usage at a server level.
Comment #4
caseyc commented@mikeytown2,
How could it not? If the only pages that require more than 128 megs are on your back end and you set the memory limit to 256 for them and 128 for the rest of the site (or possibly lower), and tune your apache settings to expect no more than 128 rather than boosting memory for the entire site and configuring apache to expect 256 megs, you couldn't *not* improve performance of your webserver. I'm not sure what value benchmarks would offer aside from the obvious, yeah?
Comment #5
mikeytown2 commentedPHP only uses what it needs. If you set the maximum to 1GB globally, and drupal takes 128mb, 1GB will not be allocated. The only way for this to work like you're hoping (increase server capacity) would be to run high memory PHP pages from the command line.