I forgot to mention -m64 flag that I also used. On 5/29/05, Vlad <marchenko@xxxxxxxxx> wrote: > ok, here is the complete details: > > Athlon64 3000+ (it's +20Mhz overclocked on the bus, i.e. running on > 220Mhz x 9 - roughly on par with Athlon64 3200+). > NForce Ultra (MB: tyan k8e) with 1Gig. > > php 5.0.4 + 1.3.33 statically compiled with -O3 -msse3 -m3dnow > -march=athlon64 -mcpu=athlon64; (can't recall if I did unroll loops > and omit frame pointer) > > no extra switches or additional modules for configure. > > the test.php script looked like > > <?php > phpinfo(); > phpinfo(INFO_MODULES); > ?> > > then tested with > /usr/local/apache/bin/ab -c 50 -n 20000 http://localhost/test.php > > FC4 x86_64, kernel is 2.6.11-1.1363_FC4 - the RPS is 730. > FC3 x86_64, latests kernel - same results. > FC3 i386, latests kernel - 570 RPS. > FreeBSD 5.4-RELEASE (x86_64, stock kernel) - 670 RPS > > same hardware in all tests, same optimization switches during compilation. > > On 5/29/05, Dave Jones <davej@xxxxxxxxxx> wrote: > > On Sun, May 29, 2005 at 06:40:55PM -0400, Vlad wrote: > > > > > I've compiled apache+php and measured max requests per second (rps) of > > > > > a simple php script (output of phpinfo(); php_info(INFO_MODULES)) with > > > > > the apache's 'ab' application. The maximum RPS I managed for FC4 is > > > > > 440 while FC3 showed up to 730. Network is not the issue cause I did > > > > > measurement via lo0. > > > > > > > > > > It's the same server and I've ran yum update before tests in both > > > > > cases. Any ideas? > > > > > > > > If you are running a kernel earlier than revision 2.6.11-1.1355, it'll > > > > have extra debugging enabled which will impact memory allocations. > > > > > > I did the tests several days ago; following your advise I just ran yum > > > update and tested once again with 2.6.11-1.1363_FC4. Things are much > > > improved now. > > > > Great! However, don't tease :-) I'm sure I'm not the only person > > curious what RPS you now achieve :-) > > > > Dave > > > > > -- > > Vlad > -- Vlad