掲示板

Connection pool tuning

8年前 に Anirudh Sharma によって更新されました。

Connection pool tuning

New Member 投稿: 2 参加年月日: 15/12/21 最新の投稿
What are the steps to set values for connection pooling? And on what parameters we can choose those values.
thumbnail
8年前 に Olaf Kock によって更新されました。

RE: Connection pool tuning

Liferay Legend 投稿: 6403 参加年月日: 08/09/23 最新の投稿
Anirudh Sharma:
What are the steps to set values for connection pooling? And on what parameters we can choose those values.


That's easy ;)

  • Decide for the application server that you want to use
  • Decide for the connection pool implementation that you'd like to use
  • (let us know of both)
  • Measure your performance with the default parameters
  • Check if - under load - you have any issues with the connection pool, or if your issues are elsewhere (e.g. memory, CPU)
  • In case you actually have issues with your connections - analyze them: You might have too many or too few connections, not check for their validity, use them too long, or anything else.


The values that you set and how to set them are dependent on

  • the implementation of your connection pool
  • The application server that you use to configure the pool
  • the result from your load-tests
  • the nature of your application (is it processing-heavy? database-intensive?)
8年前 に Anirudh Sharma によって更新されました。

RE: Connection pool tuning

New Member 投稿: 2 参加年月日: 15/12/21 最新の投稿
Thanks for the reply.

I am using liferay bundled with tomcat.

In portal.properties file there are three providers C3PO, DBCP, or Tomcat. The default provider is C3PO. What is the difference between these three providers?

Also, which of them should i use.
thumbnail
8年前 に Olaf Kock によって更新されました。

RE: Connection pool tuning

Liferay Legend 投稿: 6403 参加年月日: 08/09/23 最新の投稿
What's the difference? They're all different implementations for the same interface.

Which one should you use? Evaluate if they're actively developed & supported (depending on the service level you need). Use them in your load tests and compare their results. Then pick the one that fits your needs best (e.g. performance, memory consumption, code-maintenance etc.)