slow result

[shadowlight]

Hi,

eaccelerator is install now.

I will create you an admin account as you can review my setting and maybe optimise it a little more.


Our goal like i said is to provide 150 000 customers nearly. We currently have 50 000 customers. We are constantly with 1000 user at the same time with average of 80 request seconds.


Let me know how i can communicate with you for the admin account.


Thank you,

[shadowlight]

Hi,

I found that i have as much request processing as I have php process.


Plain SSL Max Idle Plain SSL
In Out In Out Used Avail Used Avail
22 94 0 0 2,000 14 77 1,923 0 400

Request Rate
Scope Requests in Processing Request/Second
Server 63 55
www.ixxxxxx 63 54
ApacheMain 0 0
_AdminVHost 0 1

External Apps
Scope Type Name Max CONN Eff Max Pool In Use Idle WaitQ Req/Sec
Server LSAPI phpLsapi 200 200 200 60 140 0 50


Does it means, each connect will use one phpLsapi connector ?



Thank you,

[mistwang]

Do not over-tune phpLsapi to start too many php processes, LSWS can pipe-line requests to PHP backend when there are more concurrent requests than number of PHP process. 200 should be the maximum, I recommend you try 50-100 first. Running too many PHP process may use too much memory and slow down the whole server.

[xing]

For some perspective, PHP process/children value of 20-40 is more than enough to handle millions of php pages per day provided your code is properly tuned. Setting PHP processes to a high value only if your backend/database can support that many concurrent connections and still be fast. There is no point setting PHP process pool to 100 if your mysql server will die at 50 concurrent connections.

[shadowlight]

Currently, my MySQL database is running on the same server as my litespeed daemon. With apache, i setuped my mysql to 500 connections up to 1024. it were working but I had few error about mysql cannot connect. with 100 as value for lsapiphp i had no error of this kind. Than it should be fine for now.

[xing]

For performance reasons, you need to increase "thread_cache" entry for mysql config, my.cnf, and decrease mysql's max_connection item. Unless you have a super fast disk i/o on quad core server with no table/db locking, 500 mysql connections will instantly bring your server to its knees.