fox wrote:What are you people running tt-rss on that basic js dom processing takes literal minutes? I demand to know.
server on [email protected]
, win7, postgresql+mongoose, usually 1-2% cpu usage never more than 5%
clients; same FX8320, i3 SB laptop, IBC celeron
All less than 3 years old, nothing real powerful but they handle everything else fine. None of them handled google reader much better without purging read article contents though. The load is heavier than most, about 10,000 articles a week (up to ~2000 at a time), usually less than hour to go through a day, then read the interesting articles over 2-3 hours. From a fresh load with the headline hover on, after about 50 articles it freezes the browser for 10-15 seconds, then after another 50 articles it freezes for 20 seconds and keeps getting worse, within 300 articles the ttrss tab is using 1GB, around 1.5 GB it crashes around 400 articles. Removing the headline hover it takes about 1000 articles for tab to crash but I try to close/open tab about every 500 articles, it's crawling by then, this is about the same with google reader. WIth the purge script I could keep the tab open for days, it never got above 500 MB and it never slowed down, okay maybe there was a 100ms hiccup when you fly through articles and it's purging 50+ articles every time.
UksusoFF wrote:yep, but i'm so lazy with mysql.
i'm read all article and then export\import settings =)
Good to hear, I was about to attempt it before the problem was found to not be ttrss 1.10. A new db would have been much easier for a rookie like me though.