Matthew Toseland wrote: > - Memory usage decoupled from queue size: The db4o branch "pages in" requests > on demand, so in theory can run with a relatively low memory limit, even with > a very large queue. In practice this would involve a lot of disk I/O, so it > may not work so well in practice, but at least it will degrade gradually, > rather than getting OutOfMemoryException's!
With three large downloads running, the db4o branch consistently uses about 50-70% CPU (I guess this is the paging you mentioned). The main branch uses 90-100% during startup but only 5% after that. Cheers, Michael
