Cache and the (#s) that follow it

[dane]

Good Morning - I recently upgraded the processor in my PC (running Windows 10) and it seems to have had a negative effect on topics being added to my feed. When the cache reads 400/400, there is a number in () that seems to track groups of headers being added into their proper places. In the past this would usually top out in mid single digits and take not very long to be fully acquired. Now, after the upgrade, this number is likely to rise to 14 or 15 and takes a considerable amount of time to resolve. Is this more to do with disk space than processor functioning? What are the factors that affect this process?

Thanks,
DaDane

[dane]

Nothing? Really?

[Quade]

. Now, after the upgrade, this number is likely to rise to 14 or 15 and takes a considerable amount of time to resolve. Is this more to do with disk space than processor functioning? What are the factors that affect this process?

This is probably the result of changes in how things were posted to the groups. Newsbin depends on file's to actually group to get performance. Some posting types are now NZB only. There's no information in the subject to actually do grouping.

I'm thinking about just dropping these posts instead of trying to process them.

[dane]

Thanks Quade.

[dane]

Good morning - as a follow-up to my original question, I've increased free disk space for the drive on which Newsbin lives and the process of incorporating headers has speeded up considerably.

DaDane

[Quade]

I ended up implementing the "unusable post" filter. It'll be in the next beta.

[dane]

Thanks Quade - I'll look for it.

DaDane