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
Without any limitation, percentile views can consume a huge amount of memory and processing power.
E.g. if someone decides to compute percentiles on all equals methods we would quickly get millions of data points. To prevent this, percentile views should have a configurable limit with a reasonable default to limit the number of points stored for computing percentiles.
The text was updated successfully, but these errors were encountered:
JonasKunz
added a commit
to JonasKunz/inspectit-ocelot
that referenced
this issue
Apr 22, 2020
Without any limitation, percentile views can consume a huge amount of memory and processing power.
E.g. if someone decides to compute percentiles on all
equals
methods we would quickly get millions of data points. To prevent this, percentile views should have a configurable limit with a reasonable default to limit the number of points stored for computing percentiles.The text was updated successfully, but these errors were encountered: