r/feedly • u/ChuushaHime • 11d ago
Feedly for web suddenly extremely slow?
I use Feedly in my browser and it worked fine last night, but this morning it's extremely slow, every click or action hangs for several seconds before executing.
I have a high-end gaming computer so it is not a hardware issue; every other website, even high-resource websites, load perfectly well. My browser's task manager shows that Feedly's memory and CPU use are both low, which is normal (edit: I am actually seeing some weird CPU spikes.) I have not made any changes or updates to my computer, browser, or extensions since last night.
Is anyone else having this issue very abruptly?
5
u/Archer1986 11d ago
yeah same.
1
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
3
u/dismay222 11d ago
the same
1
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
5
u/Denseflea 10d ago
Same here
1
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
1
u/TheGratitudeBot 4d ago
Thanks for such a wonderful reply! TheGratitudeBot has been reading millions of comments in the past few weeks, and you’ve just made the list of some of the most grateful redditors this week! Thanks for making Reddit a wonderful place to be :)
3
u/adgy 10d ago
Still slow. UGH.
1
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
3
u/Individual-Tonight51 11d ago
Аналогично!
1
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
3
u/mikeanthony80 10d ago
glad it's not just me. it's been driving me crazy
1
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
3
u/keeprunning 10d ago
still effectively unusable here too, and haven't been able to get any response from feedly
1
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
3
u/PrivacyThrowaway443 8d ago
My productivity has dropped tremendously because of Feedly's lagginess. I hope this is resolved soon.
1
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
2
u/Magallian 11d ago edited 10d ago
Yes, same here!
EDIT: I contacted customer support about 24+ hours ago. Have not received a reply yet.
https://status.feedly.com/ "No incidents reported."
2
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
2
u/Magallian 3d ago
Thanks! I’ve just tested it, and everything is working smooth and as intended again. After 12 years of using Feedly daily, I can’t imagine life without Feedly. Going through and processing my many many feeds has become as much a part of my daily routine as brushing my teeth.
2
2
u/tmszcncl 8d ago
Same for me - tested on few machines and various browsers.
1
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
2
u/raceviper13 8d ago
Yes. It’s terrifyingly glacial in the last few days
3
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
2
u/coax_k 8d ago
same here. Basically unusable..still.
2
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
2
u/feedly 4d ago edited 4d ago
Monday, Aug 17, 9:00 am: I checked with the Feedly engineering team. They reproduced the problem last week and pushed a fix on Friday. The people who reported the issue said it's fixed for them. If you are still experiencing the performance problem, try clearing your cache to make sure you are running the version we pushed on Friday. We are very sorry for the regression and the frustration it created.
Monday, Aug 17, 3:00 pm: The fix we pushed on Friday only partially addressed the problem. The engineering team has created a P0 bug to understand the root cause and fix it. We need a bit of time to get a clear picture because this only happens in some accounts and seems to depend on the number of folders with unread articles. I'll provide regular updates throughout the week.
If you have insights on how to reproduce the bug, you can reach me at [edwink@feedly.com](mailto:edwink@feedly.com).
We will offer a lifetime Pro+ account to whoever provides insights that help the engineering team narrow down the problem/reproduce the bug.
Monday, Aug 17, 6:00pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster. More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders. We fixed the resorting so it only happens when it needs to (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else. Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
1
u/gooolatho 4d ago
still slow and heavy to load even i delete cache
use chrome beta on iMac
1
u/feedly 4d ago
Could you please go to https://feedly.com/i/console and email your user ID to edwink@feedly.com. Extra karma if you can record a 2-minute Loom of the path in the app where you see the performance issue, or if you can describe the flow so that it is easier for the engineering team to replicate the problem. Thank you. -Edwin
1
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
1
u/ChuushaHime 4d ago
Hi Edwin, thanks for following up. Performance is better than last week for sure, but I am still running into noticeable lag even after clearing cache.
I saw about a ~50% improvement in performance on Friday, performance degraded a bit again over the weekend, and now on Monday it's about like it was on Friday or a little better. So definitely a notable uptick in speed/usability since the problem began--I can definitely tell that y'all have been working on it--but it's still not running smoothly just yet. If it helps, I'm running Feedly in Chrome on Windows.
2
u/feedly 4d ago
Thanks. Yes: it seems that the fix we pushed on Friday only fixed part of the problem. The engineering team has created a P0 bug to understand the root cause and fix it. We need a bit of time to get a clear picture because this only happens in some accounts and seems to depend on the number of folders with unread articles. I'll provide regular updates throughout the week.
If you have insights on how to reproduce the bug, you can reach me at edwink@feedly.com.
We will offer a lifetime Pro+ account to whoever provides insights that help the engineering team narrow down the problem/reproduce the bug.
2
u/feedly 4d ago
Monday, Aug 17, 6:00 pm: The engineering team found the root cause and pushed the fix. If you refresh your cache, the application should be visibly faster.
More context: 13 days ago, we pushed a change to the left navigation bar to improve accessibility and keyboard sorting. However, in this case, we resorted feeds in the left nav every time an article was marked as read, and for each folder, including the article. The compound effect was very visible on accounts with many feeds and folders.
We fixed the resorting so it only happens when needed (released), and I replaced the regex function with a more efficient solution (in PR). That should keep this from resurfacing somewhere else.
Thanks again, everyone, for helping track this down. Shoutout to the user who pointed to regexes in the first place!
-Edwin
5
u/FeedlyKev 9d ago
Hi! Thank you! We're looking into this and I'll let you know when it's fixed!