Hello,
Lately Newshosting has augmented the retention to 400 days.
Since then, when I try to update a.b.hdtv, I am always getting a message box saying "alt.binaries.hdtv cnt.dat overflow. Limit retention, headers per server, then apply retention and invoke group Compact binary-> Compact storage."
Well this doesn't work (or i didn't do it right).
What happens next is that UE stops downloading the headers for this group.
What should I do? Can I keep my settings for 400days retention or is there a limit?
Thank you
Did I hit the limit?
newshosting has now most likely the same retention as http://www.ngroups.net/ - 331 days and growing (both are highwinds servers).
the message box is not related to a retention, i just added the limit detection to prevent the program from crashing, in short cnt.dat per group cannot grow more than 4GB.
i think the current limit given this limitation is around 150M+ headers per newsgroup, for boneless i got 154M to reach 4GB.
i can increase it 2 or 4 times (i have such provision in the code, i intended to use for the search service), the question is whether it makes sense, loading time is proportional to the newsgroup size and the current limit is far more than any other newsreader allows. if to increase the limit - the database format would change as well (then per group cnt.dat would be able to grow e.g. to 8GB or to 16GB instead of currently 4GB).
so maybe you should limit retention as it prescribes, those options are in the workspace, the newsgroup context menu. open map.txt there you can find the directory number of the newsgroup, in the directory you'll see cnt.dat, e.g. if it will be 3.5GB after compacting and all headers up to date the retention will be adequate.
the message box is not related to a retention, i just added the limit detection to prevent the program from crashing, in short cnt.dat per group cannot grow more than 4GB.
i think the current limit given this limitation is around 150M+ headers per newsgroup, for boneless i got 154M to reach 4GB.
i can increase it 2 or 4 times (i have such provision in the code, i intended to use for the search service), the question is whether it makes sense, loading time is proportional to the newsgroup size and the current limit is far more than any other newsreader allows. if to increase the limit - the database format would change as well (then per group cnt.dat would be able to grow e.g. to 8GB or to 16GB instead of currently 4GB).
so maybe you should limit retention as it prescribes, those options are in the workspace, the newsgroup context menu. open map.txt there you can find the directory number of the newsgroup, in the directory you'll see cnt.dat, e.g. if it will be 3.5GB after compacting and all headers up to date the retention will be adequate.
the option wouldn't make sense, it would have the same drawbacks like "fill as much RAM as possible".
i'll check whether i can change it without changing the db format it may be possible. second option is to keep db version number somewhere so i can change database when needed, as to now the format was unchanged since v1.0 despite all additions. just the 4GB cnt.dat limit is trivial to change so no need to add any special options, the catch it i'm not sure i can change it and leave the database compatible with prior versions.
i'll check whether i can change it without changing the db format it may be possible. second option is to keep db version number somewhere so i can change database when needed, as to now the format was unchanged since v1.0 despite all additions. just the 4GB cnt.dat limit is trivial to change so no need to add any special options, the catch it i'm not sure i can change it and leave the database compatible with prior versions.
Unzipped, well... the only way to handle a file that big is not to have it all in memory at once... you have to just have a view of a small slice of it at a time.