Gwibber

extremely high cpu usage

Bug #552942 reported by d1bro on 2010-04-01

This bug report is a duplicate of: Bug #306497: gwibber uses a lot of memory. Edit Remove

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	Gwibber	New	Undecided	Unassigned

Bug Description

this is very similar to #524554 with the difference, that me am running ubuntu lucid (fresh install some weeks ago) and i never hibernated my machine.

Tags:

Revision history for this message

d1bro (d1bro) wrote on 2010-04-01:

desktop-couchdb.log Edit (14.8 MiB, text/plain)

Revision history for this message

vonskie (vonwallace) wrote on 2010-04-01:

I have the same problem...

I like gwibbler, but couchdb had to go on lucid as it would hog my cpu...

I update daily lucid...

Joshua Hoover (joshuahoover) on 2010-05-27

tags:

added: desktop+ desktopcouch

Revision history for this message

Eric Casteleijn (thisfred) wrote on 2010-08-23:

This is due to the way gwibber stores messages in couchdb and calls the views: gwibber stores each incoming message in couchdb and then queries couchdb. That means the views have to be recomputed after each and every incoming message. It's not a problem in desktopcouch. A solution would be to show the messages as they come in, and store them in couchdb every n messages in a bulk operation, and query couchdb only on startup.

affects:

desktopcouch → gwibber