Stats API
Posted: Thu Mar 12, 2020 10:41 pm
Greetings,
I've noticed the past few days (since I started assisting this project with Folding), that the stats API is extremely unreliable.
[*]Seems to take quite a while to load most of the time
[*]Good portion of the time fails altogether with 504 Gateway Time-out.
[*]Stats don't seem to be updated, or at least, I haven't been able to find the results for my team or donor name on the stats API (been running for nearly 24 hours and completed many WUs).
[*]Tried generating a passkey here, however email never came through not even to Spam folder (where the forum emails end up): https://apps.foldingathome.org/getpasskey
I know almost nothing about the science behind folding or the loads being thrown to the GPUs. However, I do have quite a bit of experience with web applications, cloud technologies, CDN's/cacheing, and email.
[*]Might we worth generating a cached copy of the stats API hourly and using a CDN to serve it up.
[*]With regards to email deliver-ability, might be worth relaying the email through more reliable email services and using DMARC/DKIM/SPF to try to improve inbox deliverability?
I'm assuming the above processes aren't already in place -- based on observed behavior of the API and the emails I've received. But if they are in-place and other issues are the cause or unknown at this time, I wouldn't mind helping out to improve systems for new comers
Aaron
I've noticed the past few days (since I started assisting this project with Folding), that the stats API is extremely unreliable.
[*]Seems to take quite a while to load most of the time
[*]Good portion of the time fails altogether with 504 Gateway Time-out.
[*]Stats don't seem to be updated, or at least, I haven't been able to find the results for my team or donor name on the stats API (been running for nearly 24 hours and completed many WUs).
[*]Tried generating a passkey here, however email never came through not even to Spam folder (where the forum emails end up): https://apps.foldingathome.org/getpasskey
I know almost nothing about the science behind folding or the loads being thrown to the GPUs. However, I do have quite a bit of experience with web applications, cloud technologies, CDN's/cacheing, and email.
[*]Might we worth generating a cached copy of the stats API hourly and using a CDN to serve it up.
[*]With regards to email deliver-ability, might be worth relaying the email through more reliable email services and using DMARC/DKIM/SPF to try to improve inbox deliverability?
I'm assuming the above processes aren't already in place -- based on observed behavior of the API and the emails I've received. But if they are in-place and other issues are the cause or unknown at this time, I wouldn't mind helping out to improve systems for new comers
Aaron