Hi
Just wanted to mention that developers who are interested in
optimising their web server performance should maybe check out
alternatives to 4D's web logging facility.
During the course of my recent marathon tests, I noticed that web
server capacity with 4D's http logging active is about 15% - 25% of
the 'logging inactive' capacity.
For example, in one typical case:
4D http Request Logging: OFF = page serving rate per hour of 45,000
4D http Request Logging: ON = page rate per hour of 12,000
With a realtime 'graphaliser' of the serving capacity, it's possible
to visually watch the serving capacity take a complete nosedive down
to a quarter of it's normal performance as soon as logging is activated.
With 'roll your own logging', the performance is hardly affected.
I speculated that the massive slowdown may be due to the fact that 4D
opens and closes the http log with every write in order to guarantee
the committal of log entries instead of leaving it open.
Regards
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
