liferea is slow on updating feeds if you have lots of feeds. multiple threads are needed for updating feeds.

Bug #227976 reported by Leon van der Ree
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
liferea (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: liferea

When I start liferea and it updates all feeds or when I press the update all feeds button, it takes a long time before I get results. It can take for more than a minute before it shows the new articles from my feeds, even though the application itself keeps responding and once the first new article is shown from the first feed, all other feeds are updated immediately.

Using the latest liferea in hardy

Multiple threads for updating feeds are needed. Otherwise it takes way too long if you have a lot of feeds. Having multiple threads for updating should also result in a less long period of disk actitivy which is good for laptop users (for example regarding the Load_Cycle_Count issue and battery life).

Revision history for this message
Leon van der Ree (lvanderree) wrote :

It turned out the second feed has got broken, which probably made liferea wait for a time-out.

But even though it does not seem to be a bug, it could use some enhancements,

1. like showing what it is doing (I could not exactly see what liferea was doing at that moment) It would be nice if the bottom toolbar would for instance not only showed: 'feed-blabla has no changes since last update' but also the task it currently is performing, like "connecting to some-feed"

2. Maybe another idea is to show in the feed-list the action which is performed on the feed, so maybe add a temporary icon to the feed which is being updated.

3. It looks like the feeds aren't updated in multiple threads, by using threads you would also solve the waiting-issue if one feed is broken and the application is waiting for a time-out. (maybe only a limited number of threads if unlimited threads would cause other issues)

Revision history for this message
ubuntu_demon (ubuntu-demon) wrote :

I'm confirming this bug. I would like to see multiple threads for updating feeds. Otherwise it takes way too long if you have a lot of feeds.

I don't agree with 1 and 2. There's already the Update Monitor (in Tools) and the lower bar of liferea also tells what it is doing.

Changed in liferea:
status: New → Confirmed
Revision history for this message
ubuntu_demon (ubuntu-demon) wrote :

Having multiple threads for updating should also result in a less long period of disk actitivy which is good for laptop users (for example regarding the Load_Cycle_Count issue and battery life).

description: updated
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

I've talked with upstream about this, and the problem isn't with downloading the feeds but with merging them in the database, which needs some time. The DB is single-threaded, so this isn't possible.

Closing as won't fix.

Changed in liferea:
importance: Undecided → Low
status: Confirmed → Won't Fix
Revision history for this message
ubuntu_demon (ubuntu-demon) wrote :

to Emilio Pozuelo Monfort:

Okay thanks for the update.

Revision history for this message
®om (rom1v) wrote :

This is not because the DB is single-threaded that this thread must be the same as the UI thread!

Changed in liferea (Ubuntu):
status: Won't Fix → Confirmed
Revision history for this message
faultygearbox (faultygearbox) wrote :

So this is not a bug, then?

Changed in liferea (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Edward Steel (eddsteel) wrote :

It seems the UI's model is directly implemented in a SQLite DB, so every UI call is blocked while accessing a DB. Nevertheless, I don't understand why the DB processing can't take place on a separate thread that updates the UI. The UI could show old information and still remain responsive!

This, very reasonable, bug report was closed upstream with no reason given. http://sourceforge.net/tracker/index.php?func=detail&aid=2880767&group_id=87005&atid=581684

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.