Forums Register Login

Scalable site

+Pie Number of slices to send: Send
While creating a large site with 10000 database connections at a time, what has to take in to account in the servlet code and where to write the JDBC connection ?
+Pie Number of slices to send: Send
10000 database connections at one time. That is not just large, that's huge. Do you really need that? Do you actually have 10000 pages in the process of being rendered all at once? Wow. If it's not a secret, what hardware and software architecture have you gone for for a site this busy, and what market generates that much traffic?
Anyway. If you don't already have it, you realy need high-performance connection pooling. Opening and closing that many connections would kill the system without ever getting any useful output. You probably want to consider data cacheing too. If a large proportion of the requests are for the same data from the database you might consider a separate thread which updates a "static" copy of the data for the servlet container(s) to return from rather than tying up the database all the time.
There are 10 kinds of people in this world. Those that understand binary get this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 547 times.
Similar Threads
Enterprise Performance
Prepared Statement
Threading strategy for the server (long)
Cleared Part I today with 79%
long post IBM.158
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 13:21:44.