In the module source, r-method is const and the comments say look, but
don't touch. That said, besides breaking the limit directive will it work?
It's poor form but it works.
It does indeed work! I'll do some further testing to make sure it doesn't
break anything else, but I think I have
http://www.phoronix.com/scan.php?page=articleitem=ubuntu_natty_pae64num=3
When it comes to running the Apache web-server in these different
configurations, there is a 3% improvement when moving from the i686 to i686
PAE kernel and 2% on top of that when moving to the x86_64 Ubuntu. With the
newer
On 4/5/2011 6:27 AM, Andrew Oliver wrote:
Anyone have any theory on why 64-bit was so much worse (suggest looking at
general article
for context rather than solely the except above)?
Simple memory access. Intel doesn't scale to 64 bits as cleanly as, say,
a sparcv9 64 bit binary vs sparcv8
That is just the thing. Other things that should have been similarly
affected in the benchmark were not. Take a gander if you would at some of
the rest of that article...
On Apr 5, 2011 11:32 AM, William A. Rowe Jr. wr...@rowe-clan.net wrote:
On 4/5/2011 6:27 AM, Andrew Oliver wrote:
Anyone
On Tue, Apr 5, 2011 at 05:55, Jason Cwik ja...@connecticinc.com wrote:
The problem is that wherever I try to insert my filter, I don't ever seem to
see the request, I only get one bucket that contains the body. Should I be
using something other than the register input filter hook? (and then
On Tuesday 05 April 2011, Andrew Oliver wrote:
That is just the thing. Other things that should have been
similarly affected in the benchmark were not. Take a gander if
you would at some of the rest of that article...
HTTPD uses lots of pointers when handling per-dir and per-module
On 4/5/2011 3:52 PM, Stefan Fritsch wrote:
On Tuesday 05 April 2011, Andrew Oliver wrote:
That is just the thing. Other things that should have been
similarly affected in the benchmark were not. Take a gander if
you would at some of the rest of that article...
HTTPD uses lots of pointers
