Update bytecode statistics
steveblackburn opened this issue · comments
Some of the bytecode statistics are out of date, and we have no statistics for eclipse because it won't trivially work (apparently due to its complex class loading behavior). This the third answer in this stackoverflow post looks promising.
Worth exploring byte-buddy.
Update. be22ce7 updated bytecode stats for all benchmarks with the following notable exceptions:
- eclipse: still does not work (has never worked)
Caused by: java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini). - spring: worked with tool prior to f6a6e97 but no longer works with recent refactoring:
java.lang.NoClassDefFoundError: org/dacapo/analysis/BytecodeCallback - tradebeans:
Exception initializing server: java.lang.NoClassDefFoundError: org/dacapo/analysis/BytecodeCallback - tradesoap:
Exception initializing server: java.lang.NoClassDefFoundError: org/dacapo/analysis/BytecodeCallback
eclipse, tradebeans, and tradesoap have empty stats-bytecode.yml files (to ensure incorrect data is not used).
spring has the recently gathered data using the analysis tool as prior to f6a6e97
Update. c9e5f0f updated the allocation statistics for all benchmarks.
Only two benchmarks lack alloc stats
- tradebeans:
WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager Exception initializing server: java.lang.NoClassDefFoundError: com/google/monitoring/runtime/instrumentation/AllocationRecorder VM was forced to quit without executing the shutdown hook - tradesoap:
WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager Exception initializing server: java.lang.NoClassDefFoundError: com/google/monitoring/runtime/instrumentation/AllocationRecorder VM was forced to quit without executing the shutdown hook
No trivial fix to the two issues above.
Merged into main