Kwok Peng Tuck wrote:
Are you sure you want to keep the connection until the webserver dies?
My webapplication connects to the database and keeps the connection open between requests, the only time connections are closes is when a webserver process stops.
Yes.
Isn't it better to release the connection back to a connection pool for reuse ? That's the way for web apps to work if I'm not mistaken.No.
Allow me to explain:
We use Apache on Linux, this means that there are a number of separate processes serving requests and that it's impossible to pass connections between instances as you would in a multithreaded server.
In front of the Apache we have a Squid running in accelerator mode, this means that a single squid process takes care of pulling the content out of the apache quickly and then feeding it to the client at whatever speed the client can accept it, so the apache is free to server another request.
This means that we have relatively few apache processes running and that the number of connections isn't that high, typically there are 10 apache processes, out of a maximum of 45 and with MAXUSERTASKS set to 300 in sapdb it doesn't come close to that limit.
The principle is the same as used in IIS (they have a number of content generation threads and one content-pushing thread, AFAIR), except MS used threads to get good performance on windows (or because it was the popular thing to do), but personally I'd rather have a stable webserver that keeps running even if a single process goes beserk.
--
Regards Flemming Frandsen - http://dion.swamp.dk
PartyTicket.Net co founder & Yet Another Perl Hacker
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
