Hello,enabling server side rendering actually *increases* TTFB for the frontend, because the server waits until it has finished rendering before it sends a response.
You can use more powerful servers for the frontend (faster CPU and/or more cores so you can increase the amount of PM2 threads), but TTFB will still be high. Caching frequently accessed pages helps a lot, either with DSpace built-in caching or by configuring apache or varnish. We've made great experiences with the latter!
We've disabled server side rendering for logged-in users (but that does require code changes), because that is faster for them and less load on our frontend server for us.
Best regards, Max Nuding On 19.09.23 04:39, Igor Baptista Da Costa wrote:
Hello,there is any thing to do in DSpace (beside all stuff in performace tuning documentation <https://wiki.lyrasis.org/display/DSDOC7x/Performance+Tuning+DSpace>, hardware upgrade and turn on server side render) to reduce the time to first byte in DSpace 7x frontend ? This issue only happens with the frontend, the backend url have a low TTFB, but the frontend TTFB is very high.Regards --All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
-- 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/35c78255-2afc-41a4-a28d-012a3c6cc73d%40uni-konstanz.de.
smime.p7s
Description: S/MIME Cryptographic Signature
