Archived

Pay attention! This repository is deprecated and all the new updates are available here.

Methods profiling results

This repository contains the profiling results of the following applications:

• derby
• dropwizard
• h2
• kafka
• micronaut
• spring-mvc
• struts2
• takes
• tomcat
• vertx

Each CSV file contains a list of methods with the number of invocations and CPU time spent in the methods.

All of that applications were profiled during one minute with a constant load of 20-50 requests per second. In general, a profiling pipeline is following:

• Start the application with profiler bytecode instrumentation by using -agentpath option.
• Start the load generator (Apache JMeter) with predefined test case.
• Initiate profiling
• Wait for a minute
• Stop profiling
• Stop the load generator
• Stop the application
• Save the profiling results

You can find all profiling scripts under main/profiling folder for each application. For example, Micronaut profiling script is located under main/profiling/micronaut folder:

• micronaut-profilinf.sh - script for starting the entire profiling pipeline.
• Micronaut.jmx - JMeter test case for Micronaut application.
• method-list-cpu.csv - list of methods with the number of invocations and CPU time spent in the methods.

All other applications have the same structure.

Note: before starting the profiling pipeline you need:

1. Download and install YourKit Java Profiler.
2. Download and install Apache JMeter.
3. Download and install the application you want to profile.
4. Change paths in the scripts according to your environment.