Hi Rubén,
you might be running into https://jira.duraspace.org/browse/DS-2904
/ https://jira.duraspace.org/browse/DS-2718. Does the behaviour
improve when you disable the Google Analytics downloads recording
(comment out the bean as described in the second issue I linked)?
There are a few other open Jira tickets related to database
connections, maybe the Community Browser was a red herring to some
extent and the actual problem is somewhere else.
https://jira.duraspace.org/browse/DS-2563 looks promising and is
currently marked as "needs volunteer".
cheers,
Andrea
On 12/01/16 23:52, Ruben Boada wrote:
Hi Andrea,
Thanks for your help and the fast response. I enabled the cache
for communities list but the problem still remaining when I run
the script requesting fast the homepage (30 connections in
Postgres immediately in use and therefore, DSpace blocked).
Cheers
El lunes, 11 de enero de 2016, 21:35:32 (UTC+1), Andrea
Schweer escribió:
Hi
Rubén,
you can reduce the load created by the community list
generator (that is
also used on the repository home page, by the way) by
enabling caching.
See here in dspace.cfg:
https://github.com/DSpace/DSpace/blob/master/dspace/config/dspace.cfg#L1943
Note the comment for this option (Manakin = XMLUI):
> # Normally, Manakin will fully verify any cache pages
before using a
> cache copy.
> # This means that when the community-list page is
viewed the database
> is queried
> # for each community/collection to see if their
metadata has been
> modified. This
> # can be expensive for repositories with a large
community tree. To
> help solve
> # this problem you can set the cache to be assumed
valued for a
> specific set of time.
> # The downside of this is that new or editing
communities/collections
> may not show up
> # the website for a period of time.
If your repo admins are DSpace super-admins, you could
instruct them to
clear the cocoon cache [2] whenever they create/rename a
collection/community, to have the change show on the
community list. You
might also like to give your repo staff a heads-up that the
community
sizes (if shown) will be cached too, so they shouldn't think
of these
numbers as 100% accurate.
Thanks a lot for mentioning this issue by the way, I too had
noticed
problems with the database connections. However, until your
e-mail made
me look at the community browser code [1], I didn't
know/remember that
the caching option exists. Note, I haven't tried it out
myself yet, but
I'm going to very shortly!
[1]:
https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/src/main/java/org/dspace/app/xmlui/aspect/artifactbrowser/CommunityBrowser.java
[2]:
https://wiki.duraspace.org/display/DSPACE/TechnicalFAQ#TechnicalFAQ-ClearingCocoon%28XMLUI%29cache
cheers,
Andrea
--
Dr Andrea Schweer
Lead Software Developer, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
+64-7-837 9120
You received this message because you are subscribed to the Google
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
--
Dr Andrea Schweer
Lead Software Developer, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
+64-7-837 9120
--
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
|
