Hi,
I also experienced performance issues in a DSpace 4.x XMLUI with a large
number of community and collection (and strength activated). After
debugging it I made two modifications that I think could be also applied
to DSpace 6.x in order to improve the performance:
1) I noted that the solr query that calculates the number of item of the
communities is called for every community and collection showed in a
request. It should be a quick request but with many communities to show
it slow down too much the request. I made this modification to hold the
item counters in static variables and calculate the counter every minute:
https://github.com/toniprieto/DSpace/commit/5855e82f78202fa4f270b30a4fc6965ee4a7dae5
2) I also noted that the code that gets the item counter is getting the
name of the community/collection though it is not used. This means that
every time you are getting the counter for a community you are
instantiating all the structure of communities and collections for
getting a name that you are not going to use. I made this modification
to avoid this:
https://github.com/toniprieto/DSpace/commit/5b953c7c9510b74fee63bb5c95ddbf9a32d7715f
I suppose that these two modifications are not the best solutions to
these problems but you could test it to check if it improves the
performance.
Thanks,
Toni
El 26/01/18 a las 11:29, Michael Plate escribió:
Hi,
Am 25.01.2018 um 16:46 schrieb Bill T:
I am recently experimenting with v6.2 as well, and I am experiencing the
same problems with community pages. This is possibly not the best
layout, but we essentially have 1 top level community which contains all
other collections and communities which number about 1000. Performance
loading this community was satisfactory in version 5.x, but has become
extremely slow in v6.x. Anonymous users see a load time of
approximately 20 seconds. Admin users see a somewhat faster load time,
approximately 18 seconds. Non-admin logged in users see a page load
time of over 1 minute. Any of these times prohibit us from going into
production with DSpace 6.
[…]
testing this,too - with the same problems; caching does not affect this
to much (xmlui.community-list.cache = 12 hours).
Our number of Communities & Collections is around 800.
In DSpace 6.2 the full view (with strength) ...xmlui/community-list
takes 75s in XMLUI.
...jspui/community-list takes < 3s in JSPUI.
Getting /rest/hierarchy (no strength, so maybe not really comparable):
real 0m0,867s
When starting debug-log of Postgresql, I can see that JSPUI uses ~ 5500
SQL-queries for community-list.
XMLUI uses ~ 23000 SQL-queries.
The structure is like
https://kobra.bibliothek.uni-kassel.de/community-list
Our setup is
RHEL 7
8 cores, 32 GB
java 1.8.0, tomcat 8.5.14
postgresql 9.6.2
[…]
ours is nearly same on Debian 9 with open-jdk (on XenServer VM).
CU
Michael
--
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.
