You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 19, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 19, 2018. It is now read-only.
Analyze the site for slow paths and optimize them #445
Under a bit more traffic and with a bit more data, the events website is practically unusable and it's constantly "loading". The codebase has some very suboptimal parts and they need to be hunted down and optimized.
Under a bit more traffic and with a bit more data, the events website is practically unusable and it's constantly "loading". The codebase has some very suboptimal parts and they need to be hunted down and optimized.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/445, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALq66_DzYf1Qf6FXiNhUdm_4er7Hlk-4ks5qzVEJgaJpZM4KVPaE.
I think I've optimized the slowest part on the homepage in 87d33bf and that made a big difference. The site seems to work fine now. I guess there's room for a lot more optimizations, but for now we should be good.
Great job Dimitar! Thank you very much for your help!
I did some tests and unfortunately the interface is still so slow that
event listing and insertion are practically unusable.
Having disabled the map, optimized the code, and upgraded the server, this
makes mi think that there is something wrong with the service that Digital
Ocean hes offered since yesterady's violation.
What do you think? I don't wee any reason for today's performance to be so
slow, considering that the site was working properly until two days ago
with much lower resources
I think I've optimized the slowest part on the homepage in 87d33bf 87d33bf
and that made a big difference. The site seems to work fine now. I guess
there's room for a lot more optimizations, but for now we should be good.
I know the site is still slow as it was not coded with volume and speed in mind so there's a lot more to be done in that regard. But since we don't have the capacity to, maybe we can at least patch here and there if it's too slow.
Under a bit more traffic and with a bit more data, the events website is practically unusable and it's constantly "loading". The codebase has some very suboptimal parts and they need to be hunted down and optimized.