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
We have a series of applications that run 24/7 for months and months at a time. Should I be concerned about ever increasing memory use by Metrics.NET - or is the internal data-structure set up to have a finite size?
This is a conceptual question, and I am not actually interested in one specific use-case, so the number of metrics, counters, meters and so on should not matter. However, there might be different concerns in regards to how metric-types use memory over time perhaps?
Finally, will using any reporters have an impact on the above? I guess not, but find that I have to ask :)
The text was updated successfully, but these errors were encountered:
We have a series of applications that run 24/7 for months and months at a time. Should I be concerned about ever increasing memory use by Metrics.NET - or is the internal data-structure set up to have a finite size?
This is a conceptual question, and I am not actually interested in one specific use-case, so the number of metrics, counters, meters and so on should not matter. However, there might be different concerns in regards to how metric-types use memory over time perhaps?
Finally, will using any reporters have an impact on the above? I guess not, but find that I have to ask :)
The text was updated successfully, but these errors were encountered: