I have completed debugging database leaks, file leaks and related issues in
requests, inserts and site inserts, including cancelling mid-request. Thus,
the remaining work:
- Create some failures artificially in requests, inserts, and site inserts;
most of the testing has been on successful fetches. See that they don't leak.
This should take a few days, I'm fairly confident in the code because of the
mid-request cancellation testing so far.
- Bucket ownership tracking. At the moment, the db4o branch has no way to
recover persistent temporary file space lost due to bugs. Bucket ownership
tracking would resolve this. It will be tricky to introduce after merging, so
implementing it before merging probably makes sense. However it will probably
take at least a week including debugging.
- Preference in scheduler for recently succeeded requests. A form of this
exists on trunk, not implementing it before merging would result in a
performance regression. This should take a few days including debugging.
- Think about automatic database backup. Should be fairly easy, 1 day.
- Run the ULPR tests as a sanity check (should be trivial, 10 minutes).
- MERGE DB4O.
- Fix plugins to work with db4o.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20090331/b01e98d9/attachment.pgp>
