You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A large portion of the slowdown is related to the existing client re-establishing a new client and connection for each request. The large outliers though that I have still not tracked down.
We have seen similar behavior with requests for static route resources which suggests that the outliers are not rfd-api or vm specific. It is possible that we have some kind of bottleneck with our network appliances that sit in front of rack 3.
Independent of the above results, search responses return excess data and should be trimmed down to make sure we are only querying from our backed the exact necessary data.
Activity
augustuswm commentedon Nov 28, 2023
A large portion of the slowdown is related to the existing client re-establishing a new client and connection for each request. The large outliers though that I have still not tracked down.
augustuswm commentedon Dec 11, 2023
We have seen similar behavior with requests for static route resources which suggests that the outliers are not
rfd-apior vm specific. It is possible that we have some kind of bottleneck with our network appliances that sit in front of rack 3.augustuswm commentedon Mar 11, 2024
Independent of the above results, search responses return excess data and should be trimmed down to make sure we are only querying from our backed the exact necessary data.