Susan, I have only seen this in cases where I have forgotten to setup PostgreSQL vacuumdb. Some things require more intensive database queries, while others only require searching Lucene indexes, which explains the inconsistent slowness. My postgres datbase user has a cronjob like:
0 6 * * * /postgresql/pgsql/bin/vacuumdb --analyze dspace > /dev/null 2>&1 If you are doing this already, then look for other reasons the dspace webapp may be hitting the database really hard, like Google indexing. Quoting "Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS]" <[EMAIL PROTECTED]>: > Hi, > > We have been noticing that in our Production instance of DSpace, > version 1.4.2, that the response time is very, very slow when you click > on a Community. This only happens when you click on a Community name. > Response time when you click on a Collection is fine. Also, the > response time for a search is really fast. So I'm wondering why the > response time is soo slow for Communities. Anyone have any ideas?? > > Thanks a bunch, > > Sue > > > > > > Sue Walker-Thornton > > ConITS Contract > NASA Langley Research Center > </></>Integrated Library Systems Application Administrator/DBA > > 130 Research Drive > > Hampton, VA 23666 > > Office: (757) 224-4074 > Fax: (757) 224-4001 > Pager: (757) 988-2547 > Email: [EMAIL PROTECTED] > > > > ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
