Slow performance Dspace 6.2

[christian criollo]

 Hi all

Recently I installed Dspace 6.2 when I give click in a community, collection or item it takes too long to respond normally it should be a few seconds    what t could be happenning ?

 thanks for the help

[Alan Orth]

Hello, Christian.

You need to give us more information before we would be able to help you. For example:

- Operating system version

- PostgreSQL version

- Java version

- Tomcat version

- Hardware specifications of your server, like RAM and CPU

Regards,

--
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 dspace-tech...@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

--

Alan Orth
alan...@gmail.com
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch

[christian criollo]

Hi Alan

this is my configuration

- Operating system version  R/  SUSE Linux Enterprise Server 11 (x86_64)

- PostgreSQL version R/ the database is Oracle Database 11g Release 11.2.0.3.0 - 64bit

- Java version R/ java version "1.7.0_45"

- Tomcat version  R/ 7.0.50

- Hardware specifications of your server, like RAM and CPU R/ three proccesors Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz  RAM  5994588 kB

I hope htis help

[Alan Orth]

Hello,

Your server should have enough power to run DSpace well. Is there anything else running on the server? How much of the machine's RAM is dedicated to the Java JVM heap? You can look in the "Java Information" section of the control panel when logged into DSpace as an administrator. Also, is your DSpace a clean installation or is there a lot of content submitted in it?

Regards,

[christian criollo]

Hi Alan

I find the reason of slowly and the problem it was indexes database  in the table metadatavalue that strangely not executed the scripts are the next:

CREATE INDEX metadatavalue_object on metadatavalue(dspace_object_id);
CREATE INDEX metadatavalue_field_object on metadatavalue(metadata_field_id, dspace_object_id);

I executed this scripts and the performance of the  application improve noticeably already respond in seconds that is the normal

thanks for your attention and help

[Alan Orth]

Good to know, Christian. I don't use Oracle so I'm not sure, but I assume that these indexes were supposed to be created by DSpace during installation. Must be a bug.

Regards,

[Tim Donohue]

All,

Just verifying that these indexes are supposed to be created automatically (for either Oracle or Postgres) as they exist in the 6.0 database migration scripts:
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/resources/org/dspace/storage/rdbms/sqlmigration/oracle/V6.0_2015.03.07__DS-2701_Hibernate_migration.sql#L368

It sounds like the migrations may not have all completed successfully. Not sure why that would be. The logs from the initial installation may have provided more information as to whether the "V6.0_2015.03.07__DS-2701_Hibernate_migration" migration succeeded or not.  You also could double check that your database reports successful migrations by running [dspace]/bin/dspace database info   (This command reports the current database status, and a larger table that lists all database migrations and whether each has run successfully on the database.)

Good luck,

Tim

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

[christian criollo]

Hi Tim

Thanks for  the answer in the initial instaaltion the logs shown the migration was successfully and the table schema_version too, this is not the only problem what i have had

[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.

Other community pages are faster, depending on the number of sub collections/communities, but still too slow for production and much slower than v5.x

Our setup is

RHEL 7

8 cores, 32 GB

java 1.8.0, tomcat 8.5.14

postgresql 9.6.2

This should be more than enough in terms of hardware and software, and ran DSpace 5 successfully.

Is there anybody in the community with a similarly sized instance (1000 communities and collections, 60,000 item records) running DSpace 6?

Tom Desair addressed an even worse problem in the 'select collection' page of the submission form about a year ago;  Is there a similar problem on the community pages? (Sorry to pick on you Tom, that's what you get for being helpful).

Any questions/comments/suggestions will be appreciated.  We would love to upgrade, but just can't with the performance I'm seeing.

Thanks!

Bill

[Tom Desair (Atmire)]

Hi Bill,

No problem ;-). I just have a few questions:

1. How does the "/community-list" page performance of 6.2 compare to DSpace 5?
   
2. Are you using JSPUI or XMLUI?

Best regards,

Tom

 

Tom Desair 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 Gaston Geenslaan 14, Leuven 3001, Belgium www.atmire.com

[Hardy Pottinger]

Hi, there is a wiki page for performance tuning DSpace, you might check it out:

https://wiki.duraspace.org/display/DSDOC3x/Performance+Tuning+DSpace

Alan's right, mostly it boils down to tuning your Tomcat memory settings. Note that this advice only aplies to Tomcat 7 and earlier. During boot-up, Tomcat 8 will explain to you patiently that the old heap settings will be ignored every time you try to set them. So, a potentially easier thing to do would be to move to Tomcat 8, as it will automatically better utilize the memory it has available to to it.

--Hardy

To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscribe@googlegroups.com.

To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

--

Alan Orth
alan...@gmail.com
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch

--
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 dspace-tech+unsubscribe@googlegroups.com.

[Bill T]

Hi Tom!

/community-list performance is bad and worse!

DSpace 5.7 approx 18 seconds (this has always been a slow load -- we simply don't link to it)

DSpace 6.2 approx 80 seconds

we use xmlui

Oh, and the indexes mentioned in an earlier post HAVE been created...

Cheers!

Bill

[Bill T]

Thanks Hardy!

I'm on tomcat 8.5 already, and my startup options are pretty simple:

CATALINA_OPTS="$CATALINA_OPTS -Djava.awt.headless=true

  -Djava.library.path=/usr/local/tomcat-native.lib

  -Dfile.encoding=UTF-8

  -Xms16384m -Xmx16384m

  -Dsolr.autoSoftCommit.maxTime=120000 -Dsolr.autoCommit.maxTime=4800000"

That's half my available RAM, and this is a dedicated machine.  Nothing else is running on it (well, except postgresql).  These settings served me very well when running DSpace 5, but if you have any other suggestions I would love to try them out!

Cheers!

Bill

[Bill Tantzen]

From my control panel, while my top-level community is loading simultaneously:

Runtime statistics

Available processors: 8
Maximum memory: 16247 MiB
Allocated memory: 16247 MiB
Used memory: 4030 MiB
Free memory: 12216 MiB

It appears that I have plenty of available memory...
Bill

[Michael Plate]

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

[Tom Desair]

Hi Bill,

No problem ;-). I just have a few questions:

1. How does the "/community-list" page performance of 6.2 compare to DSpace 5?
   
2. Are you using JSPUI or XMLUI?

Best regards,

Tom

 

Tom Desair 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 Gaston Geenslaan 14, Leuven 3001, Belgium www.atmire.com

To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscribe@googlegroups.com.

[Toni Prieto]

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ó:

[Ying Jin]

Hi Bill,

We are experiencing the same performance issue with 6.2. Although our community pages load OK, but still much slower than v5.x. Some of our collections will time out to load or take several minutes to load. They are not big collections, one of them only have 20 items, but each items contains 100+ bitstreams. The postgresql left so many "idle in transaction" processes that will slow down the overall site. The tomcat begin to take most of the CPU time too.

We used to use 16G of memory for tomcat under v5.x, and the performance has been ok. Now, even I increased to 64G(half of our server memory) under 6.2, the performance didn't improve. 

BTW, we are using Tomcat 8.0.13, Java 1.8, Redhat Linux 6.7, and XMLUI. We have about 80+ communities, 280+ collections, 60,000+ items and 490,000 bitstreams. 

Is this a common issue with 6.2?

Best,

Ying

[Gustavo Tonini]

We are also experiencing the same issue on DSpace 6.2 at https://repositorio.ufsc.br. The access to /community-list takes minutes to complete. Turning on the item counter (strength) makes things much worse. We have hundreds of communities and more than 100K items.

[Bill T]

Gustavo,

There is also some discussion taking place on this topic here: https://groups.google.com/forum/#!topic/dspace-tech/VIofW7EwEXY

I'd love to figure this out!!

--Bill