Re: [PATCH 2] Re: [PATCH] performance patch for mod_log_config

2001-09-10 Thread Brian Pane
dean gaudet wrote: [...] >but still, does this really work? 'cause the time used is >r->request_time, if a request takes longer than 14 seconds or so to >generate/serve then the logger is going to be asking for timestamps which >are dangerously close to your cache rollover. and since you can'

Re: [PATCH 2] Re: [PATCH] performance patch for mod_log_config

2001-09-10 Thread dean gaudet
On Mon, 10 Sep 2001, Brian Pane wrote: > dean gaudet wrote: > > > why is there a need for 15 entries? if it's a multiprocess server then > > there's only a need for 1 or 2 entries. if it's a multithreaded server > > then you need to lock the cache (which you're not doing :) > > The whole point

Re: [PATCH 2] Re: [PATCH] performance patch for mod_log_config

2001-09-10 Thread Brian Pane
dean gaudet wrote: > why is there a need for 15 entries? if it's a multiprocess server then > there's only a need for 1 or 2 entries. if it's a multithreaded server > then you need to lock the cache (which you're not doing :) The whole point of the design is to do the multithreaded cache with

Re: [PATCH 2] Re: [PATCH] performance patch for mod_log_config

2001-09-10 Thread Ryan Bloom
On Sunday 09 September 2001 23:51, Brian Pane wrote: > Cliff Woolley wrote: > >On Sun, 9 Sep 2001, Brian Pane wrote: > >>I think putting it in APR would work. The one limitation I can think of > >>is that adding the cache in apr_explode_localtime() itself wouldn't be a > >>win because we'd have t

Re: [PATCH] performance patch for mod_log_config

2001-09-10 Thread Alex Stewart
Brian Pane wrote: > William A. Rowe, Jr. wrote: > >> Is this the right place to be caching, or should this become a >> straightforward >> optimization to apr's time.c functions? I'd think the advantages are >> many for >> keeping 15 current seconds in apr, and would pay off across the >> boar

Re: [PATCH 2] Re: [PATCH] performance patch for mod_log_config

2001-09-10 Thread dean gaudet
why is there a need for 15 entries? if it's a multiprocess server then there's only a need for 1 or 2 entries. if it's a multithreaded server then you need to lock the cache (which you're not doing :) isn't the real win in eliminating both the divisions required by the explode time functions an

[PATCH 2] Re: [PATCH] performance patch for mod_log_config

2001-09-09 Thread Brian Pane
Cliff Woolley wrote: >On Sun, 9 Sep 2001, Brian Pane wrote: > >>I think putting it in APR would work. The one limitation I can think of >>is that adding the cache in apr_explode_localtime() itself wouldn't be a >>win because we'd have to add the overhead of a gettimeofday() call to >>check wheth

Re: [PATCH] performance patch for mod_log_config

2001-09-09 Thread Cliff Woolley
On Sun, 9 Sep 2001, Brian Pane wrote: > I think putting it in APR would work. The one limitation I can think of > is that adding the cache in apr_explode_localtime() itself wouldn't be a > win because we'd have to add the overhead of a gettimeofday() call to > check whether the supplied time was

Re: [PATCH] performance patch for mod_log_config

2001-09-09 Thread Brian Pane
William A. Rowe, Jr. wrote: >Is this the right place to be caching, or should this become a straightforward >optimization to apr's time.c functions? I'd think the advantages are many for >keeping 15 current seconds in apr, and would pay off across the board. Within >apr, we can always recalcula

Re: [PATCH] performance patch for mod_log_config

2001-09-09 Thread Cliff Woolley
On Sun, 9 Sep 2001, William A. Rowe, Jr. wrote: > Is this the right place to be caching, or should this become a > straightforward optimization to apr's time.c functions? I'd think the > advantages are many for keeping 15 current seconds in apr, and would > pay off across the board. Within apr,

Re: [PATCH] performance patch for mod_log_config

2001-09-09 Thread William A. Rowe, Jr.
l, for fun. Bill - Original Message - From: "Brian Pane" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, September 09, 2001 9:46 PM Subject: [PATCH] performance patch for mod_log_config > The call to apr_explode_localtime() in mod_log_config is one of

Re: [PATCH] performance patch for mod_log_config

2001-09-09 Thread Cliff Woolley
On Sun, 9 Sep 2001, Brian Pane wrote: > The call to apr_explode_localtime() in mod_log_config is one of the more > expensive operations in the httpd. This patch attempts to reduce the > overhead by caching the result. Looks quite reasonable... I wouldn't mind seeing this as an ap_ function, sin

Re: [PATCH] performance patch for mod_log_config

2001-09-09 Thread Brian Pane
Ryan Bloom wrote: >On Sunday 09 September 2001 19:46, Brian Pane wrote: > >Can we get this as a unified diff? > sure, here's the unified form: Index: modules/loggers/mod_log_config.c === RCS file: /home/cvspublic/httpd-2.0/modules/l

Re: [PATCH] performance patch for mod_log_config

2001-09-09 Thread Ryan Bloom
On Sunday 09 September 2001 19:46, Brian Pane wrote: Can we get this as a unified diff? Ryan > The call to apr_explode_localtime() in mod_log_config is one of the more > expensive operations in the httpd. This patch attempts to reduce the > overhead by caching the result.

[PATCH] performance patch for mod_log_config

2001-09-09 Thread Brian Pane
The call to apr_explode_localtime() in mod_log_config is one of the more expensive operations in the httpd. This patch attempts to reduce the overhead by caching the result. --Brian Index: modules/loggers/mod_log_config.c === RCS