3 ms·
GitHub's API does't provide the exhaustive list of all your contributions. Instead we crawl GitHub's website which is slow. Details at https://github.com/Aurel
by brillout 8y ago
GitHub's API does't provide the exhaustive list of all your contributions. Instead we crawl GitHub's website which is slow.
Details at https://github.com/AurelienLourot/github-contribs#how-does-it-work https://github.com/AurelienLourot/github-contribs#how-does-i...
We are in talks with GitHub and they know that we are crawling GitHub.
- ChristianBundy 8y ago> Instead we crawl GitHub's website which is computationally expensive I'm surprised to hear that you're bottlenecking on CPU time. Could you verify that my understanding is correct? I would've thought your bottleneck would be networking and connectivity as you have to wait for GitHub to process all of the requests.
- rjacksonm1 8y agoLooks like they're hitting a GitHub rate limit, rather than bottlenecking on CPU.
- brillout 8y agoYou're right. I edited my answer. The GitHub's unofficial API we are using is slow and per IP rate limited. We spin up several servers to have several IPs to circumvent the rate limit. (GitHub knows that we do that and we are in contact with them.)
- exikyut 8y agoIf GitHub are okay with you using multiple IPs to get that data then it's not inherently expensive on their side for you to be using this. Surely a rate-limit exception could be in order, then? And perhaps you could help them alpha-test a new API endpoint that just so happens to include all the info rolled up as one URL :D (Hmmmmm.... GraphQL....)