Hello Andreea,

If you are still experiencing less than ideal performance, we have some
notes on improving the performance of DSpace by providing more memory to
it:  https://wiki.duraspace.org/display/DSDOC6x/Performance+Tuning+DSpace
 While the *minimum* values there are good for brand new sites, as you site
grows in size or has a large number of users, you really should be looking
at allocating several GB of memory for Tomcat alone. Very large or very
active sites tend to be in the 2-4GB or more range.  If your memory
allocation is too small, your site performance will suffer, and DSpace will
become slower and slower.

It's hard to say if this is your exact issue, but it's usually the first
thing to check when performance is less than ideal.  Others on this mailing
list may have more specific advice to add here.

Tim




On Mon, May 20, 2019 at 2:35 AM Andreea Oprescu <andreeamopre...@gmail.com>
wrote:

> Thank you for your answers. I will check into your proposed solutions.
> Yes, its dspace 6.2 with xmlui.
>
> I've been reading around a bit, but I still wonder why mydspace is so
> slow. Is it because of bitstreams? My items don't have more than 4-5
> bitstreams...
>
> El viernes, 17 de mayo de 2019, 11:10:00 (UTC+2), Andreea Oprescu escribió:
>>
>> Hello everyone,
>>
>> I am currently trying to debug a* very slow* dspace implementation. I am
>> facing the following issues:
>>
>> - organization with more than 2.624 collections, in 4 communities, which
>> at the same time have 5, 5, 52 and 19 subcommunities.
>> - users and administrator accounts. Users accounts with less permissions
>> take a lot longer to process than administrator accounts (does dspace check
>> all the permissions of an user in ALL the collections?)
>> - there seem to be a lot of SQL queries. For example, for moving an item,
>> I ended up with almost 6000 SQL queries, which took a little bit more than
>> 2 minutes to complete (for admin account).
>>
>> I think dspace is a wonderful tool which provides my organization a lot
>> of value, but it's really, really slow.
>>
>>
>> => Is it normal, because of the amount of data?
>> => Are we implementing something wrong?
>> => If this is not normal, do you have any guides or advices on how to
>> procede with the debugging?
>>
>>
>> I have tried to find information about this, but could only find this
>> post, with the same problem, but no responses:
>> http://dspace.2283337.n4.nabble.com/Very-slow-quot-Move-item-quot-button-td4687571.html
>>
>>
>> I really appreciate your time.
>> Regards,
>>
>> Andreea.
>>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/7d8bbdc8-bd92-493f-8768-ce95f1587011%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/7d8bbdc8-bd92-493f-8768-ce95f1587011%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 

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

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CACKSJ9Nsi4wE%3DXxkHPRtMyzMJ47Q_OnoLR1s%2BUor_RHBoM5aSg%40mail.gmail.com.

Reply via email to