Hey Majo! You're a lifesaver! Of course I had one pm2 instance! Now I have 11 of them and the server is doing a lot better! [image: 2023-11-16_182827.png] Still, the response in not instant. I think the response time depends on the performance of one pm2 instance and one CPU core (which is not the best in my case). But at least the server is not chocking with multiple requests. That is a very big deal! Amazing. Thank you! The speed index is 1-2s now instead of 5s! That is acceptable.
Best regards, Andrew четвер, 16 листопада 2023 р. о 15:47:21 UTC+2 dataquest пише: > Hi, it is me again! > > Hrafn, there are many many many REST calls every time any page loads. I do > not think the issue will be mitigated > by the update you mention. > > Andrew, your pm2 configuration does not seem to be correct at all. > I have 7 nodes and it looks like this: > [image: image.png] > From what you posted, it seems you only have one node running, which would > explain a lot. > I am not sure if you are using dspace-ui.json (or similar) config file for > pm2, if so, check if you have > line such as this: > "instances": "7" > I know the -i parameter on command line should set this and I have no idea > why you apparently only have > one node, but it might be a good idea to try this. I also found that for > certain settings, I have to do > pm2 delete dspace-ui.json > and then > pm2 start dspace-ui.json > > merely using pm2 restart dspace-ui.json was not sufficient, perhaps that > is what happened. > > The anon chache only starts having effect, if your server is not clogged > up by other requests. If it is, > requests that could be served from cache will probably spend some time > waiting, therefore being slow > anyway. > > Time to live = 3 hours is way too long, I have 10 seconds and it is fine. > > In my humble opinion, your biggest problem is only having one node on pm2. > If you do not resolve that, I wouldn't expect other fixes to have much > effect on anything. > > Make sure you see several nodes listed, just like in my screenshot. Then > you can start looking > into other optimizations. > > Best regards, > Majo > > > > On Thu, Nov 16, 2023 at 2:32 PM Hrafn Malmquist <hrafn.m...@gmail.com> > wrote: > >> Hi guys >> >> I would consider upgrading to 7.6.1. There are a few performance fixes in >> this bug release: >> >> https://wiki.lyrasis.org/display/DSDOC7x/Release+Notes#ReleaseNotes-7.6.1ReleaseNotes >> >> Specifically https://github.com/DSpace/dspace-angular/issues/2482. A bug >> where a page load would make 1 or 2 unnecessary GET calls to the server >> depending on the path. Upgrading to 7.6.1 should therefore reduce server >> load. >> >> Best regards, Hrafn >> >> On Wed, Nov 15, 2023 at 3:48 PM Andrew K <pkm...@gmail.com> wrote: >> >>> Hi Mayo! >>> >>> Sure, I looked to pm2 first thing >>> This is what I have >>> [image: 2023-11-15_171420.png] >>> I guess it's OK, cluster mode. >>> I added "exec_mode": "cluster" in dspace-ui-json >>> I also use "pm2 start >>> /home/dspace/dspace-angular-dspace-7.6/dspace-ui.json -i max" >>> Per your advice I am going to change it to a number less than cores #. >>> As soon as know how much cores I can get) >>> >>> Based on my understanding, once the page loads, it runs in your browser. >>> Only when you refresh, >>> open it on new window (or for some other reason download the whole page >>> from server) is it slow. >>> When it is downloaded and runs in browser, it only executes some calls >>> to backend, which is fast. >>> This would agree with your observations. >>> >>> >>> Ah. Thanks! That explains a lot. >>> But then I can not understand the main page loading so long *when the >>> anon cache is enabled*. >>> The main page should be cached 100%. >>> But it always loads as if there's no cache... It actually looks like it >>> loads as long as for a logged user. >>> I have >>> anonymousCache: >>> max: 50 >>> timeToLive: 7200000 # 3 hours >>> allowStale: true >>> >>> That should work, right? >>> >>> Best regards, >>> Andrew >>> >>> -- >>> 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 dspace-tech...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/dspace-tech/c5c92992-7a5f-4efa-abb6-7d6a55e43341n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/dspace-tech/c5c92992-7a5f-4efa-abb6-7d6a55e43341n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> 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 dspace-tech...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/dspace-tech/CAG9P5m9%3DZb14u2gKvfmxeGcVcg8SPVd-bbHOgPLZ2OZhK7RQ5A%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/dspace-tech/CAG9P5m9%3DZb14u2gKvfmxeGcVcg8SPVd-bbHOgPLZ2OZhK7RQ5A%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/ccc9c04c-1c33-4f1b-acac-0d6cbe06b7d2n%40googlegroups.com.
