Re: Persistent Sessions in DB connection for QZDASOINIT, implemented by Nathan -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Walden H. Leverich skrev:

I have in the last few months been the user of a high -profile, high-traffic web site
...
Essentially I'd like to avoid a similar situation where I'm responsible
...
If there are no immediate brickwalls ahead in the planned scenario, then keep it simple. I.e. a connection per user.

I'm not trying to put words in other people's mouths, but I'm not sure your conclusions are supported by the conversation. I think the big question is, what's "high-traffic". I think there is agreement that in low-traffic sites the one-connection-per-user approach works. I know I agree with that, and I'm a proponent of not doing sites that way :-). I think there is also agreement that the one-connection-per-user approach would _not_ work for mega-traffic sites like Amazon, Facebook or MySpace. So the question is, what's "high-traffic"? Is it 100 simultaneous users? Nope. 1000? Maybe... 10,000 Probably...

Perhaps "high traffic" could be defined as "enough to hit a limit in the KISS solution"?

Whatever limit has been reached varies, but in my experience it is typically the response time in the database.

/Thorbjørn

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.