On Thu, 1 Mar 2001, Bill Stoddard wrote: > FWIW, last week I wrote a very simple memory allocator (apr_malloc(), > apr_calloc(), apr_free()) and replaced all the malloc/calloc/free calls in the > apr-util/buckets with the apr_* calls. It was good for a 10% performance > boost serving static pages on Windows. My allocator used intraprocess apr > mutexs which are implemented as Win32 CriticalSections. There are probably > better sync objects available (compare and swap) which would be good fora few > more %. > > If anyone is interested, I'd be happy to post it to the list in all it's > unfinished/unrefined glory. Sounds very interesting... I'd like to take a look at it. Thanks, Cliff
- some reasons why Apache 2.0 threaded is slower than... Ian Holsman
- Re: some reasons why Apache 2.0 threaded is sl... Bill Stoddard
- Re: some reasons why Apache 2.0 threaded i... Cliff Woolley
- Re: some reasons why Apache 2.0 thread... Bill Stoddard
- Re: some reasons why Apache 2.0 threaded i... William A. Rowe, Jr.
- Re: some reasons why Apache 2.0 threaded is sl... Cliff Woolley
- Re: some reasons why Apache 2.0 threaded i... Jeff Trawick
- Re: some reasons why Apache 2.0 thread... Cliff Woolley
- Re: some reasons why Apache 2.0 th... Rodent of Unusual Size
- Re: some reasons why Apache 2... Bill Stoddard
- Re: some reasons why Apache 2... Greg Stein
- Re: some reasons why Apac... Jeff Trawick
- Re: some reasons why ... Greg Stein
