#53 Use shelve instead of sqlite for cache db - dupeGuru

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#53 ✓invalid

Use shelve instead of sqlite for cache db

Reported by Virgil Dupras | September 1st, 2009 @ 09:06 AM

sqlite cache db for dgpe brings lots of problems (like #45), and the possibility of switching to shelve for a cache db should be contemplated.

However, the change must be benchmarked! Getting blocks from the DB is a very important bottleneck of dgpe.

Comments and changes to this ticket

Virgil Dupras September 5th, 2009 @ 06:59 PM
- State changed from “new” to “accepted”
- Tag changed from “pe, task” to “pe”
[not-tagged:"task" state:"accepted" bulk edit command]
Virgil Dupras January 20th, 2010 @ 09:49 AM
- State changed from “accepted” to “invalid”
Bah, now that I removed the threaded mode from all Cache instances in PE, and now that Clear Picture Cache doesn't choke on corrupted DB anymore, I'm not sure it's such an important problem. I'm sure shelves bring their own lot of problems too.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.