Performance concerns on "fe.disroot.org"/soapbox frontend.

PresGas commented

2021-12-10 15:40:49 +01:00

I am noticing a definite performance lag with the new ActivityPub instance especially on initial load of page and sometimes first click to another area after the home page loads (like the local timeline, for example). Site seems reasonably responsive after this point so far.

Browser becomes slow to unresponsive for a couple of seconds. Mobile browser especially impacted (Android with FF Nightly). I am also seeing hesitation with both FF snap and deb package.

This user is still looking at what info to pass on to group, but creating issue for others to be pointed at. Looking at various FF web tools from the desktop version.

I am noticing a definite performance lag with the new ActivityPub instance especially on initial load of page and sometimes first click to another area after the home page loads (like the local timeline, for example). Site seems reasonably responsive after this point so far. Browser becomes slow to unresponsive for a couple of seconds. Mobile browser especially impacted (Android with FF Nightly). I am also seeing hesitation with both FF snap and deb package. This user is still looking at what info to pass on to group, but creating issue for others to be pointed at. Looking at various FF web tools from the desktop version.

fede added the

bug

🤔️ Investigate

labels 2021-12-10 17:09:15 +01:00

fede added the

Akkoma

label 2021-12-10 17:10:41 +01:00

PresGas commented

2021-12-11 20:33:46 +01:00

Author

Possible example thread that impacted the browser greatly:

https://fe.disroot.org/@thegibson@hackers.town/posts/AEItU1ZeFTMxxPXlDs

Possible example thread that impacted the browser greatly: https://fe.disroot.org/@thegibson@hackers.town/posts/AEItU1ZeFTMxxPXlDs

muppeth commented

2021-12-12 10:37:08 +01:00

Owner

Interesting. I thought this was caused by me having as usual over 200 tabs open and my laptop running on the edge of ram/cpu. I have now opened the link you posted and indeed the entire browser is affected by this. It will be good to check logs both server side and browser side and submit it upstream to soapbox, I have a feeling it something with the frontend. Thanks for pointing this one and submitting link we can use to reproduce.

As for mobile, I would not put too much effort into it as there is plenty of clients so using browser for AP services is just bad choice on mobile anyway and should be discouraged.

Interesting. I thought this was caused by me having as usual over 200 tabs open and my laptop running on the edge of ram/cpu. I have now opened the link you posted and indeed the entire browser is affected by this. It will be good to check logs both server side and browser side and submit it upstream to soapbox, I have a feeling it something with the frontend. Thanks for pointing this one and submitting link we can use to reproduce. As for mobile, I would not put too much effort into it as there is plenty of clients so using browser for AP services is just bad choice on mobile anyway and should be discouraged.

PresGas commented

2021-12-12 17:09:47 +01:00

Author

Yeah, I also have a tonne of tabs open and this is the first page that has killed the whole thing. I wanted to use some of the FF web developer tools, but if the whole browser is impacted; not sure what would work. Is there anything I can send your way to help?

WRT mobile front ends, I strongly feel that a responsive web front end should come first over apps/api for your typical user. Idealistically, I would rather have as few mobile apps as possible esp if there is a perfectly fine web front end. I do feel that if the overall front end performance is improved the mobile browser experience will follow.

Yeah, I also have a tonne of tabs open and this is the first page that has killed the whole thing. I wanted to use some of the FF web developer tools, but if the whole browser is impacted; not sure what would work. Is there anything I can send your way to help? WRT mobile front ends, I strongly feel that a responsive web front end should come first over apps/api for your typical user. Idealistically, I would rather have as few mobile apps as possible esp if there is a perfectly fine web front end. I do feel that if the overall front end performance is improved the mobile browser experience will follow.

PresGas commented

2021-12-12 18:04:44 +01:00

Author

Another thing to report but not sure how to measure is a possible memory leak/resource hogging even after I close the tab. I have a couple of FF threads at the top of htop and my fan running hard even after closing the tab. I had to quit the browser to fully calm the machine down.

PresGas commented

2021-12-13 01:44:45 +01:00

Author

I am not able to get the Web Developer Tools to come online enough. I am getting from the FF console numerous Out of memory errors.

I also attached a screenshot from about:processes showing that example link above makes a tab process rocket up to 5GB!! This was also a new profile without any addons; so pretty fresh.

I am not able to get the Web Developer Tools to come online enough. I am getting from the FF console numerous Out of memory errors. ![image](/attachments/23aaf2bb-96ef-4b2e-95e9-ff675e36cb85) I also attached a screenshot from `about:processes` showing that example link above makes a tab process rocket up to 5GB!! This was also a new profile without any addons; so pretty fresh.

Screenshot_2021-12-12_19-40-27.png

52 KiB

image.png

37 KiB

PresGas commented

2021-12-14 16:37:35 +01:00

Author

Putting these here for safe keeping (in case we are wondering about postgres):

https://docs-develop.pleroma.social/backend/configuration/postgresql/

and

https://blog.soykaf.com/post/postgresql-elixir-troubles/

Problem I am seeing seems to still point at client/js, but why not look at DB tuning for scaling as "fe.disroot.org" gets out of beta.

Putting these here for safe keeping (in case we are wondering about postgres): https://docs-develop.pleroma.social/backend/configuration/postgresql/ and https://blog.soykaf.com/post/postgresql-elixir-troubles/ Problem I am seeing seems to still point at client/js, but why not look at DB tuning for scaling as "fe.disroot.org" gets out of beta.

fede commented

2021-12-15 17:25:44 +01:00

Owner

Started to have the same issue just a couple of days ago, though I also noted this slowness to load from the begining of the instance (but I thought it was my internet connection). I had to change the web shortcut URL in order to avoid the landing page which sometimes takes forever to access.

PresGas commented

2021-12-15 21:00:57 +01:00

Author

I browsed the upstream dev's instance and did not have the sort of resource utilization as "fe.disroot.org"'s front end nor did the browser hang or hesitate.

PresGas commented

2021-12-19 23:44:54 +01:00

Author

@muppeth switching to dev branch fixes performance issues on front end.

https://fe.disroot.org/@muppeth/posts/AEZkNOcy03dwIYyFRw

I would consider this closed, but will let the team officially close it just in case muppeth wants this as a reminder to implement autobuild.

@muppeth switching to dev branch fixes performance issues on front end. https://fe.disroot.org/@muppeth/posts/AEZkNOcy03dwIYyFRw I would consider this closed, but will let the team officially close it just in case muppeth wants this as a reminder to implement autobuild.

PresGas commented

2021-12-19 23:48:44 +01:00

Author

Closing.

PresGas closed this issue

2021-12-19 23:48:44 +01:00

Performance concerns on "fe.disroot.org"/soapbox frontend. #177