case 1: large J2EE based integration scenario with a lot of services, in
different .ears/.sars: about 20
datasources with connection pool size of 20 - 50 each, No Idea about the CPUs,
it was some Solaris Zone
We had some performance problems with the asynchronous part of the application,
so we
Hi all,
even after reading all the replies I'm still not convinced that
there must ba relation between the pool size and the core/cpu number.
IMHO the storage subsystem plays an important role.
I think that it's more important focusing on the average db call
duration and calcultating the
Hi all,
I've been studying a few large enterprise applications and have noticed an
interesting trend... many of these apps have HUNDREDS of connections (like
600) available or even open in their connection pools...
Survey Questions:
1. How many connections do you have available in your pool?
Ours is an application that requires guaranteed response times under 50 ms,
so:
1) We dropped using any kind of pool, so that
2) number of constantly open connections equals to the number of processors
(16)
3) I know you were asking about pool, but still I dared to respond with this
no-pool
It sounds like you're still using a pool, but your max, min, idle, and
active connections are all equal (i.e. 16). Otherwise, how do you allocate
connections to the incoming requests?
Cheers,
Clinton
On Tue, Jan 20, 2009 at 12:33 PM, Nicholoz Koka Kiknadze kikna...@gmail.com
wrote:
Ours is
Hi Clinton,
I apologize ahead, if I am missing or not getting
something right. As far as my understanding goes, arent number of
connections in a pool in relation to the number of parallel users that
access the application than the number of CPU cores in a database?
Regards
S
On
We have a pool of 16 threads (one per cpu) with a single connection
assigned per thread, so its rather a thread pool...
On Tue, Jan 20, 2009 at 2:39 PM, Clinton Begin clinton.be...@gmail.comwrote:
It sounds like you're still using a pool, but your max, min, idle, and
active connections are all
Hi Sundar,
I am not an hardware expert, but I suspect that even with modern dma access
etc if you ask your CPU to process N database transactions (initiated by
different users) in parallel it may take longer compared to when you ask it
to do them consequently. So quite possible that pools with
Thanks Nicholoz!
I have never ever questioned people for
having so many connections. But that was the reason what I have always got,
i.e, Connections being propotionate to number of parallel users. I just
brought the question about because, I wasnt surprised at all
I am no expert in this either but a default setup for oracle allows for 200
connections. At least this was the case a few version back. In my mind I
think you can an maybe should have more connections than processors.
Depending on the length of time the connection is open and idle. Again I
So all this being said what is the general rule of thumb for setting
up pool sizes?
On Tue, Jan 20, 2009 at 5:43 PM, Nathan Maves nathan.ma...@gmail.com wrote:
I am no expert in this either but a default setup for oracle allows for 200
connections. At least this was the case a few version
Absolutely. In addition to general resource contention (CPU, Disk I/O
etc.), you also have to consider lock contention against the database tables
themselves. Relational databases do not scale well in this regard. Throw
as much CPU power and hardware against your database as you like, as soon
Thanks So much Clinton. That was terrific!
-Sundar
On Tue, Jan 20, 2009 at 9:12 PM, Clinton Begin clinton.be...@gmail.comwrote:
Absolutely. In addition to general resource contention (CPU, Disk I/O
etc.), you also have to consider lock contention against the database tables
themselves.
@ibatis.apache.org
cc
Please respond to Subject
user-j...@ibatis. [SURVEY] How many
By no means am I an expert in this field, but last year I was working on a
large app. The DB guy had pretty impressive knowledge, not just about
databases but also app servers and connecting to DB¹s in general. He had
done some performance monitoring on a number systems with varying loads and
15 matches
Mail list logo
