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

Cache not behaving, getting many 'Too Many Requests' on identical URLs #5

Open
wjdp opened this issue Nov 10, 2016 · 3 comments
Open

Comments

@wjdp
Copy link
Owner

wjdp commented Nov 10, 2016

Too Many Requests --- ... --> https://github.com/newtheatre/history-project/

Should only hit URL once, and use cache after that

@wjdp wjdp added the bug label Nov 10, 2016
@wjdp
Copy link
Owner Author

wjdp commented Nov 10, 2016

Only happens when concurrency is turned on (TestFilesConcurrently: true)

@ssbarnea
Copy link

Any updates?

@wjdp
Copy link
Owner Author

wjdp commented Dec 29, 2019

@ssbarnea Concurrent mode has not seen any development of late. Beyond running multiple external requests simultaneously (at a reduced rate to prevent this issue) I don't foresee much performance improvement over what we get today. (Mostly somewhat informed speculation, would be happy to be proven wrong!)

As external link checking results are cached this really is a "nice to have" so unless someone else wants to look into this I doubt there will be much movement any time soon. Sorry!

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

2 participants