-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jasdeep,
jasdeep wrote: > Yes this is peek load actually .. The requests are through SMS's which > is forwarded by kannel server to my application . actually we are in > development phase and we are testing it as per client specifications. > > So this was the load client specified ... i had set the max limit of > my pool to 100 ... that may be the problem . i will go and increase it > now... If you need to serve 200 requests per second, ten you need to evaluate what percentage of requests result in DB connection use, and then estimate the number of those that are simple SELECTs versus more complex queries. I'll bet that many of your requests use connections for a very short amount of time, while others take more time. You need to either estimate or observe that pattern (and you can only estimate right now, since you're only in the dev phase) and then plan the size of your connection pool based upon that. This is crude capacity planning. If each connection lasts 1 second (a long time) and uses a DB connection through the entire request-response cycle, then you'll need exactly 200 connections in your connection pool (plus a few extra for good measure). 200 connections to your database might get very heavy, especially for Oracle (which at least /used/ to be known for very very heavy server-side connection memory requirements -- the db server, not the app server). Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGVDV19CaO5/Lv0PARAkEPAJ9UlPFD76jlZcTwEUr4Hf4jQXQj0gCfUzM3 ZE3Nb1DdqEh44WPc5l4EoZ8= =60Zz -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
