Skip to content

greasyfork.org slow to respond #973

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Procyon-b opened this issue Aug 12, 2021 · 1 comment
Closed

greasyfork.org slow to respond #973

Procyon-b opened this issue Aug 12, 2021 · 1 comment

Comments

@Procyon-b
Copy link

(for me, now is: 12/8 14:30 GMT+2)
Since at least yesterday (24h, maybe even 36-48h) greasyfork.org is slow to respond. It is sometimes even slower than uso.

I've browsed a little, then timed the display of the homepage. Sometimes it loads in a couple of seconds, but it can often take 10 to 40s to respond and then another 5-10 seconds to finish loading (I don't ad-block gf). Same with other pages.

Yesterday I was debugging the updating method used by stylus. In the network tab of the extension, greasyfork.org was the slowest to respond. Sometimes up to 20-30 seconds just for one connection. So it's not just the user's website that is slow.

@JasonBarnabe
Copy link
Collaborator

JasonBarnabe commented Aug 12, 2021

Thanks for reporting - I've been away the past few days.

This appears to be an effect of #884 - script's mentions (e.g. when you @ a user) get duplicated in some circumstances, and after numerous doublings, a script can have thousands of mentions. This causes problems when loading a script's previous version, as it has to recalculate some aspects of this. These requests essentially caused 100% CPU load and took an extremely long time to complete, which affected other requests.

I've cleared the bad data, put in a sanity check, and will look into fixing #884 properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants