Typically, Java app servers do support JDBC connection pools in addition
to incoming thread connection pools. So you should see dramatically
lower #connections to the database when you run the Java version.
Shanti
Xuekun Hu wrote:
Hi, Guys
In Olio/PHP, each user will usually create one connection to web
server, and then one connection to mysql end. With more than 20k
users, the number of connections are huge from mysql view I thought.
It will consume lots of memory and meet the potential lock contention,
thus the scaling should be bad if supporting huge number of users. I
thought in real setup, middleware usually is implemented a thread
pool, with limit number of connections to db end. All the user
requests will go through the thread pool to db end. With this
architecture, db could do higher throughtput than
one-user-one-connection-one-thread model.
I wonder is it possbile to implment a thread pool in Olio/java?
Thx, Xuekun
