Profiling procedure:

  1. Deploy fcrepo-webapp
  2. Fire up YourKit and attach to Tomcat
  3. Open the Jmeter Fedora Profiling Test Plan
    1. Set NUM_THREADS=1 and LOOP_COUNT=100
       
    2. Enable (toggle) only:
      1. HTTP Authorization Manager
      2. Fedora 4Run the JMeter Threadgroup "Fedora 4 Create Object"
      3. Fedora Basic Test/Create Object
    3. Run to create some new objects
    4. Disable Fedora Basic Test/Create Object and enable Fedora Basic Test/Delete Object and run again
  4. Start the CPU Sampling in YourKit
  5. Let YourKit collect data for some time
  6. Click on "Capture Snapshot" to stop profiling and open the results.
  7. Look at Hotspots in YourKit results

 

 

Profiling setup:

  • No labels

1 Comment

  1. Andrew Woods

    These results are consistent with the profiling seen on other operations. It would appear that the JGroups configuration is the source of the most significant time sinks:

    • DataInputStream.readInt()

    Hopefully, the Tracker item to deactivate JGroups when running in single-server mode will eliminate this issue.
    https://www.pivotaltracker.com/s/projects/684825/stories/51314651 

     

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.