gwibber-bugs team mailing list archive

[XceptN <727132@xxxxxxxxxxxxxxxxxx>]

Thanks.. Indeed that helps a bit with the performance 
- but -
that does not help with the file size. Eventually the sqlite database will get very large and it would cause problems (like it was 1.5GB before I deleted the previous one). Problems like disk space, backup problems etc. I believe a user should have the option not to log everything or at least clean the logs.

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/727132

Title:
  gwibber.sqlite grows too big and causes gwibber to hang

Status in Gwibber:
  New

Bug description:
  I am following more than 18000 accounts by my twitter account. I think
  just because of that the ~/.config/gwibber/gwibber.sqlite file grows
  very fast.

  Before I cleared all my gwibber configuration and started fresh the
  file was 1.5 GB of size and every refresh, operation on Gwibber was
  taking 5 minutes where the application seemed to hang.

  After I cleared the configuration and restarted, just within a day,
  the file became 18MB and it is growing rapidly.. Causing every
  operation to become slower and slower.

  I also have another Twitter account to follow and Facebook, but I do
  not want to integrate them before this problem is solved..

  AFAICS every message coming in to the Gwibber is stored in
  gwibber.sqlite. If there would be a feature to cleanup of tweets /
  messages on the GUI, it would solve my problem.

  My Setup:
  - Ubuntu 10.04 32-bit
  - Gwibber 2.32.2
  - Only one twitter account where it follows more than 18000 other twitter accounts