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
Every so often a customer using OData Client in a long-running service reports consistent high memory usage after making a request that returns a large payload. This issue can usually be resolved by disabling entity tracking and/or using short-lived/scoped DataServiceContext instances (e.g. one per request) instead of a long-lived shared one. We should add a section in the perfomance guidelines doc that talks about this.
Every so often a customer using OData Client in a long-running service reports consistent high memory usage after making a request that returns a large payload. This issue can usually be resolved by disabling entity tracking and/or using short-lived/scoped DataServiceContext instances (e.g. one per request) instead of a long-lived shared one. We should add a section in the perfomance guidelines doc that talks about this.
Sample customer issue: OData/odata.net#3019
The text was updated successfully, but these errors were encountered: