Also here is a graph.


On 14 January 2013 14:48, helix84 <[email protected]> wrote:

> Here are my db options from dspace.cfg of that instance (default
> except raised db.maxconnections):
>
> # Maximum number of DB connections in pool
> db.maxconnections = 90
>
> # Maximum time to wait before giving up if all connections in pool are
> busy (milliseconds)
> db.maxwait = 5000
>
> # Maximum number of idle connections in pool (-1 = unlimited)
> db.maxidle = -1
>
> # Determine if prepared statement should be cached. (default is true)
> db.statementpool = true
>
>
> Hilton, what do you use for db.maxidle? I'm wondering if that could be
> what makes a difference.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>



-- 
*Hilton Gibson*
Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa

Tel: +27 21 808 4100 | Cell: +27 84 646 4758
http://library.sun.ac.za
http://scholar.sun.ac.za
http://ar1.sun.ac.za
http://aj1.sun.ac.za

<<attachment: postgres_connections_ALL-year.png>>

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to