Expose runtime settings & stats for metrics scraping and diagnostics #335
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I frequently find myself attaching these via FFI for closer inspection, so I figured they may be worthwhile to have available by default.
Metrics for allocations and open files:
Vips.tracked_mem
- bytes currently allocatedVips.tracked_mem_highwater
- max bytes allocatedVips.tracked_allocs
- current allocation countVips.tracked_files
- current open file countExpose global settings for inspection:
Vips.vector?
- whether SIMD vector support is enabledVips.cache_max
- max operations to cacheVips.cache_max_mem
- max bytes to cacheVips.cache_max_files
- max open files to cacheUpdated the corresponding Ruby setter methods to return the new value rather than
nil
.