Clustered/Distributed/Load Balanced all out Joomla! - Joomla! Forum - community, help and support

hi folks,

this should of interest setting clustered or distributed or load balanced environment.

the problem: i'm getting 2 4 "requests per second" on joomla vs hundreds using plain html pages. what's going on , can better performance cluster? figured it's time post , ask thoughts.

i've spent past year or 2 putting makings of should solid setup multi joomla site interested in offering. however, suffering such performance problems fear not work unless can figure out what's going on.

first, infrastructure.

-i've set redhat clustering , gfs centralized storage.
-the storage units 12-drive raid partitions on fibre channel networking. dual channel, dual path redundancy , replication well.
-ip on ethernet , storage on fibre channel noted above.
-using lvs primary , redundant servers load balancing front end.
-all web servers (nodes) see storage if own, not shared such in nfs, centralized storage , gfs allows each node have read/write access directly. of course means 1 set of web sites/pages web servers have access to.
-separate image servers handle images offload web servers.
-separate 8-way cpu mysql servers 16gbram.

not sure else should add if need know something, ask please.

i've been trying test performance needed sort of starting point have been using ab , apachetop testing.

at first, thought problem might gfs related doesn't appear after all. problem *seems* joomla itself. i've tested gfs partitions , without , obvious results have been joomla.

i found 'requests per second' changed based on applications , not based on wether being served gfs partition or not. have no doubt gfs plays role in performance loss not great difference seeing between applications. seems, @ least.

i ran these tests stand alone, non clustered server , pointed both load balancer , directly web server. results same i'll post load balancer;

this gfs mounted web root , joomla application test page;
# ab -k -n 100 -c 100 http://192.168.1.150/

time taken tests:  57.43335 seconds
requests per second:    1.75 [#/sec] (mean)
time per request:      57043.335 [ms] (mean)
time per request:      570.433 [ms] (mean, across concurrent requests)
transfer rate:          26.03 [kbytes/sec] received

this without gfs mounted web root , simple index.html test page;
# ab -k -n 100 -c 100 http://192.168.1.150/

time taken tests:  0.187115 seconds
requests per second:    534.43 [#/sec] (mean)
time per request:      187.115 [ms] (mean)
time per request:      1.871 [ms] (mean, across concurrent requests)
transfer rate:          267.22 [kbytes/sec] received

same test without gfs mounted , different lamp application;
# ab -k -n 100 -c 100 http://192.168.1.150/

time taken tests:  0.241493 seconds
requests per second:    414.09 [#/sec] (mean)
time per request:      241.493 [ms] (mean)
time per request:      2.415 [ms] (mean, across concurrent requests)
transfer rate:          215.33 [kbytes/sec] received

same test without gfs mounted , joomla application;
# ab -k -n 100 -c 100 http://192.168.1.150/

time taken tests:  35.653875 seconds
requests per second:    2.80 [#/sec] (mean)
time per request:      35653.873 [ms] (mean)
time per request:      356.539 [ms] (mean, across concurrent requests)
transfer rate:          26.11 [kbytes/sec] received

questions;

1 - best settings use joomla , php.ini joomla applications?
2 - there things joomla not lend standard testing doing? perhaps there other tests should trying instead?
3 - if have more thoughts on can test, more willing try them out. use couple of things.

mike

well, how large of of site this?  numbers way low setup (i've benchmarked joomla @ around 800 requests/second on single dual xeon server running mysql localhost).  mambots/modules using?  how many database queries running?  caching enabled?