Collecting profiles for guided optimizations
←Older revision | Revision as of 08:50, 30 August 2019 | ||
Line 9: | Line 9: | ||
With this kind of setup the whole orchestration of the containers is simplified. Development produces [[JAR]] files of the application and operations can distribute them to [[Docker]] containers. When needed, they can selectively enable the profiles gathering via a remote [[JMX]] connection. Later they can retrieve the collected data via the same JMX connection and provide them back to development to use them when generating the final [[NativeImage]] binary. | With this kind of setup the whole orchestration of the containers is simplified. Development produces [[JAR]] files of the application and operations can distribute them to [[Docker]] containers. When needed, they can selectively enable the profiles gathering via a remote [[JMX]] connection. Later they can retrieve the collected data via the same JMX connection and provide them back to development to use them when generating the final [[NativeImage]] binary. | ||
- | This all was working in [[GraalVM]] EE 1.0 RC14. Since RC15 it needs an additional option '''-XX:-UseJVMCINativeLibrary ''' to (temporarily) disable the '''libgraal''' compiler. Btw. [[AOTMadeFaster|Improving performance of GraalVM native images with profile-guided optimizations]] shows how to use the functionality in [[GraalVM]] EE 19.2.0. | + | This all was working in [[GraalVM]] EE 1.0 RC14. Since RC15 it needs an additional option '''-XX:-UseJVMCINativeLibrary ''' to (temporarily) disable the '''libgraal''' compiler. Btw. [[AOTMadeFaster|Improving performance of GraalVM native images with profile-guided optimizations]] post shows how to use the functionality in [[GraalVM]] EE 19.2.0. |
<!-- GR-13626 --> | <!-- GR-13626 --> | ||