-
Notifications
You must be signed in to change notification settings - Fork 0
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
Massive Warning spikes in Proposal Backend #914
Massive Warning spikes in Proposal Backend #914
Comments
There are a few batch methods on UOWS we could look at - Scheduler does something similar GetBasicPeopleDetailsFromUserNumbers might be a good start. |
|
We have limited the amount of proposals to 200 at a time because users was not able to keep up loading 15k proposals. The best solution should be to do a batch request to users if possible as suggested. |
Thanks for your comments , I was not sure if we need to do any further changes. I will look into this. |
As per my analysis so far, User-office-backend is making N+1 round trips to database/UOWS when fetching principal investigator details, while resloving the Proposal query. Best approach to solve this would be using graphql/dataloader for batching requests to UOWS. However, There is another option type-graphql-dataloader, which I believe we can use? I have done a small poc with this lib and it does the batching, but it has a dependency on If there are any other potential options which we can consider, I'm open to them. |
I have tried using type-graphql-dataloader in our project set up, but it is not compatible with |
@Bhaswati1148 In case it's useful at all I've sent you a joining link for apollostudio |
Thank you @srconway , I shall have a look into this. |
We have been seeing massive warning spikes in our logs every couple of days:
The issue seems to be when an Instrument Sci or UO is getting all the proposals it is calling the
getUser
endpoint on the UOWS for every principal investigator and if the UOWS isn't available at that moment it causes all these warnings. We should try and batch these requests to the UOWS through a batch loader.The text was updated successfully, but these errors were encountered: