by itimpi » Tue Mar 29, 2011 12:14 pm
In v6 the headers are initially downloaded into a rv4 file and then processed into a .db3 database. The .rv4 files are removed after being processed. The processed header information is stored in the .db3 databases. This .db3 file does not shrink as headers are removed - instead the space merely gets marked internally for re-use. This means that for a given group it tends to grow until the number of headers in the database reaches a steady value and then the database stays at that size. This is the trade-ff that v6 makes - the additional space required to store the information in a database to get the extra speed of access and reduced memory footprint at a later stage when loading and processing Post lists.
I guess one could run a sqlite3 "vacuum" command on the database and that would reclaim any unused space, but it could take a long time to run on a large database.
Last edited by
itimpi on Tue Mar 29, 2011 12:15 pm, edited 1 time in total.