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
{{ message }}
This repository has been archived by the owner on Jul 16, 2022. It is now read-only.
We should create a benchmark to measure the overall overhead that monitoring with ZIO ZMX adds to an application. This is going to vary between applications, but we should create an application that does significant "real work" as well as monitoring that work. Measuring the execution time with and without monitoring will give us a metric for how much ZMX monitoring is "costing" in terms of performance. We can then assess this to confirm that it is appropriately low and measure the impact of optimizations.
The text was updated successfully, but these errors were encountered:
This should be done on a metric client specific basis at this point as the functionality provided by this library is specific to particular metric clients.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should create a benchmark to measure the overall overhead that monitoring with ZIO ZMX adds to an application. This is going to vary between applications, but we should create an application that does significant "real work" as well as monitoring that work. Measuring the execution time with and without monitoring will give us a metric for how much ZMX monitoring is "costing" in terms of performance. We can then assess this to confirm that it is appropriately low and measure the impact of optimizations.
The text was updated successfully, but these errors were encountered: