gwibber_messages couchdb views use more disk space than needed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Invalid
|
High
|
Unassigned | ||
gwibber (Debian) |
Invalid
|
Undecided
|
Unassigned | ||
gwibber (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Lucid |
Won't Fix
|
High
|
Unassigned |
Bug Description
A lot of the views in the gwibber_messages couchdb database emit doc as the value. This is unnecessary, as any view can me made to return the document in its rows by calling it with the parameter include_docs=true, and I believe it wastes a lot of disk space, as the views are stored in their entirety. On my machine, with somewhere around 50K messages in gwibber, the database (after compaction) takes 78MB, whereas the views for it take over 1GB.
I have started work on a branch that fixes this, which should be pretty small, but it's a little more work than I expected, absent any kind of tests. I'll try to add tests for the changes I make at least.
(Another space saver is to use much shorter document ids. It looks like gwibber generates its own ids, so I'd suggest encoding the uuids to base64 to use less bytes or something. Obviously I'm polluting my own bug here, I just wanted to make note of it somewhere in case I forget to follow up on it.)
Changed in gwibber: | |
assignee: | nobody → Eric Casteleijn (thisfred) |
Changed in gwibber: | |
milestone: | none → 2.30.0 |
importance: | Undecided → High |
milestone: | 2.30.0 → none |
status: | New → Confirmed |
Changed in gwibber (Ubuntu): | |
status: | New → Triaged |
Changed in gwibber (Ubuntu): | |
importance: | Undecided → High |
Changed in gwibber: | |
status: | Confirmed → Fix Committed |
Changed in gwibber (Ubuntu Lucid): | |
assignee: | nobody → Mikhail Turov (groldster) |
assignee: | Mikhail Turov (groldster) → nobody |
Changed in gwibber (Debian): | |
status: | New → Invalid |
Changed in gwibber: | |
assignee: | Eric Casteleijn (thisfred) → nobody |
This bug is fix committed from 2010-03-18 and gwibber 2.29.94 was released on 2010-04-01 is this bug fixed?