gss parameters for tuning performance

[GoogleCodeExporter]

What are recommended settings for tuning the gss service?

I changed max pool size on each server from 10 to 150 since 10 connection got 
used really fast and no new ones could be used. 

in gssdb-ds.xml:

<min-pool-size>1</min-pool-size>
<max-pool-size>150</max-pool-size>

I changed locking timeout in solr to 20/10 seconds since I ran into some 
locking timeouts with solr:

in solrconfig.xml

<writeLockTimeout>20000</writeLockTimeout>
<commitLockTimeout>10000</commitLockTimeout>

Is there anything left to tune for performance?

Regards,
Nikola

Original issue reported on code.google.com by ngara...@gmail.com on 1 Feb 2012 at 10:24

[GoogleCodeExporter]

150 connections in the pool is too much. We have run into low performance in 
the past after increasing the pool size too much. If I remember correctly we 
have something around 50.
We also have increased the number of searchers in solr configuration from 2 to 
20.

Original comment by chstath on 1 Feb 2012 at 10:59

• Added labels: Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

But what if all connections are used up and I cannot establish new ones? 
Increasing number of solr searchers only aids in search performance?

Original comment by ngara...@gmail.com on 1 Feb 2012 at 11:03

[GoogleCodeExporter]

If you have such a high demand, you can increase the pool size but then maybe 
you will need more memory/cpu. You have to monitor performance and make your 
decisions.
Number of searchers help with search performance and in cases where you need to 
rebuild the search index.

Original comment by chstath on 1 Feb 2012 at 11:13