Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting the overview file can take a long time #9

Open
LegalizeAdulthood opened this issue Jun 5, 2024 · 2 comments
Open

Getting the overview file can take a long time #9

LegalizeAdulthood opened this issue Jun 5, 2024 · 2 comments
Assignees
Milestone

Comments

@LegalizeAdulthood
Copy link
Owner

Current version trn can take a long time to get the overview file on my local ISP.

Investigate this with the updated trn and see if there's something we can do about speeding this up.

@LegalizeAdulthood LegalizeAdulthood added this to the 5.0 milestone Jun 5, 2024
@LegalizeAdulthood
Copy link
Owner Author

LegalizeAdulthood commented Nov 4, 2024

Using strace it was observed that when entering a newsgroup, trn does a LISTGROUP with no arguments. This results in the server traversing the newsgroup's entire store to identify the valid numbers of all articles. It's probably starting a counter at the minimum article number and doing a file existence check for every number from the low to high article numbers for the group, resulting in a very lengthy and disk intensive process for a newsgroup with many articles, e.g. comp.os.vms on my server.

At a minimum, trn should be using the .newsrc to identify the range of article numbers that need to be listed. It should probably be using the overview support in NNTP to do something better as an alternative.

@LegalizeAdulthood
Copy link
Owner Author

LegalizeAdulthood commented Nov 4, 2024

This all takes place in find_existing_articles

@LegalizeAdulthood LegalizeAdulthood self-assigned this Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant