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
Some metrics on how many bytes of JFR files are written to disk by pyroscope.java would help adjust disk size and give us confidence to more broadly enable continuous profiling
A nice to have would be a distribution of file sizes so we can estimate the "worst case" when applications with larger JFR files are unluckily scheduled on the same kubernetes node
Use case
Similar to #1960, we are being cautious about using up to much disk space
The text was updated successfully, but these errors were encountered:
Request
Some metrics on how many bytes of JFR files are written to disk by
pyroscope.java
would help adjust disk size and give us confidence to more broadly enable continuous profilingA nice to have would be a distribution of file sizes so we can estimate the "worst case" when applications with larger JFR files are unluckily scheduled on the same kubernetes node
Use case
Similar to #1960, we are being cautious about using up to much disk space
The text was updated successfully, but these errors were encountered: