Thanks for the responses received.
Your suggestions and checks have already been put into action. Some of
them showed great promise and have already been implemented.
Currently, the repository is exhibiting "normal" response times, except
during episodes of very high traffic. These instances involve certain
robots, traffic fromTurnitin and other data extractors, along with
significant institutional load.
Under normal circumstances, we are experiencing a manageable load across
the various elements of the architecture. The backend, frontend, Solr,
and database servers are operating at a medium-low usage level. We have
also established 8 PM2 threads, among other measures.
As we prepare for the anticipated high-activity peaks in September, we
are interested in gathering your insights regarding the most effective
strategies for expanding our architecture. It seems that we might have
reached the limit of vertical growth. Should we contemplate the addition
of a second frontend server? Would this prove beneficial during
instances of extremely heavy load? Any guidance or tips you could
provide would be greatly appreciated.
Thank you for your ongoing support.
Emilio
On 13/07/2023 22:29, DSpace Technical Support wrote:
'd also recommend that anyone using DSpace 7.5 consider enabling the
new "caching of server-side rendered pages" feature for anonymous users:
https://wiki.lyrasis.org/display/DSDOC7x/Performance+Tuning+DSpace#PerformanceTuningDSpace-Turnon(orincrease)cachingofServer-SideRenderedpages
Simply put, one of the areas where a site can see slowness (especially
to the homepage) is during "server-side rendering". Each time a user
visits your site, the *first* page they receive is flat HTML (which is
dynamically built via server-side rendering). This is a feature of
Angular which tries to speed up the initial page by sending immediate
HTML while the Javascript app is still downloading... once the
Javascript app finishes, it replaces the flat HTML and allows you to
interact with the page.
However, on very complex pages or pages with a lot of content (like
the homepage) , the server-side rendering can take time/resources to
generate that flat HTML *on demand*. That's why we've added the
caching feature to cache these flat HTML pages for anonymous
users....it ensures that the server-side rendering runs *less
frequently*, and the same flat HTML page can be cached & returned for
many anonymous users. That said, this caching is *disabled by default
*at this time.
We've enabled this caching on https://demo7.dspace.org/ to allow the
homepage to load more rapidly.
Take a look at the docs here for more information:
https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Configuration#UserInterfaceConfiguration-CacheSettings-ServerSideRendering(SSR)
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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 view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/1479ecf5-d5b4-dec0-7dab-1481ca362484%40arvo.es.
