6.50 RC3 behind the scenes question...

by SnakeByte (Posted Thu, 14 Nov 2013 13:16:18 GMT)

Quade wrote:I noticed it in the title.

Newsbin tries to process the GZ files in the order that works best for the user. So, it scans and sorts the GZ's into group order so, the currently visible groups are imported first. That works fine for normal usage. 200 or so, GZ files, process a couple, then check to see if the more GZ's showed up that apply to this group. I think what you're seeing is the folder enumerator and because you have a crazy group count, you also have a high GZ count so, the design probably falls down some, for your usage pattern. If it wasn't for user interaction, it would scan once then process. 6.42 worked that way. It meant people with currently loaded groups, might not see their new headers for awhile while the backlog got processed.

What use case would involve gz files populating in the import folder outside of newsbin's knowledge? Certainly newsbin knows when it just downloaded and saved something to disk. Why not put an entry in the import queue the moment the saved file is closed and leave parsing the import folder for stray gz files as something that only happens on application start? Then newsbin would only have to reorder the gz cache queue to prioritize for open group tabs.

Also, even with a high gz count, and even if this polling is necessary, it shouldn't be necessary to traverse the import folder more than one time after a download of the headers through, right?

If the user has no group tabs open, should it even be attempting any of this?

Read Main Topic

---