14 Mar
2007
14 Mar
'07
3:57 p.m.
Papadopoulos Georgios wrote:
...
Another issue that came up is the number of
connections from Openser to
the database. In our case, listening to five interfaces, with tcp
disabled and children=5, we get 28 connections to DB which is a great
waste of resources. From those five interfaces, one is receiving the
bulk of traffic and the rest receive minimal traffic. Since each child
has its own connection, then what is the purpose of connection pooling?
How difficult would it be to have a common connection pool for all children?
I don't think that having 28 DB connections is a waste of resources, in
fact I think you will get better DB query performance using one DB
connection per openser worker process than using a DB connection pool.
Most databases including Oracle DB are optimized for concurrent access
using either a process or a thread pool, so why not take advantage of
that. And most DBs can easily handle at least 100 concurrent DB connections.
Christian
sorry for the long email and thank you in advance for
any answer.
George
Disclaimer
The information in this e-mail and any attachments is confidential. It
is intended solely for the attention and use of the named addressee(s).
If you are not the intended recipient, or person responsible for
delivering this information to the intended recipient, please notify the
sender immediately. Unless you are the intended recipient or his/her
representative you are not authorized to, and must not, read, copy,
distribute, use or retain this message or any part of it. E-mail
transmission cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses.
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users