Thanks Mark. We have the upgrade of PostgreSQL on the to-do list. I guess we're going to have to make it a priority. By the way, I did bump up max_connections from 30 to 100 yesterday and did see some improvement when clicking on "Communities and Collections", clicking on a Community or Collection, and clicking on an actual item, but the browse by subject, author, title, and date are all still very slow. What do you have the buffers set at in postgreSQL.conf? Thanks, Sue
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark H. Wood Sent: Thursday, February 28, 2008 8:48 AM To: [email protected] Subject: Re: [Dspace-tech] Poor response time in DSpace 1.4.2 You could try increasing max_connections in postgresql.conf. But it's possible that connections are not closing properly and that will eat up as many as you care to permit, eventually. If you're running some ancient v7.x release of PostgreSQL, upgrade to at least 8.0. I used to see this problem, and upgrading the PG components seems to have cured it. On a lightly-used production instance here I'm running with max_connections = 100. That's on PG 8.0.8, and I'm bugging the Gentoo PG team to find out why we're stuck at 8.0 when 8.3 is in beta and 8.2 has been out and stable for many months. On the java side I'm using the postgresql JDBC driver v8.1-404. -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is "intuitive" he means the exact opposite. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
