Summary

Environment

Speed

Memory

Jetty Startup

• Until end message is printer
• Done by hand with a chronometer

First Access

• First HTTP request after starting Jetty

First access to not existing page without UI (/xwiki/bin/get/NoSpace/NoPage)

• Firefox network statistics to load the root resource (image/js/css/etc. resources are not taken into account).

First access to not existing page with UI (/xwiki/bin/get/NoSpace/NoPage)

• Firefox network statistics to load the root resource (image/js/css/etc. resources are not taken into account)
• Done by hand with a chronometer

Reload

• XWiki is doing nothing on background and everything is both in server and client cache already
• Firefox network statistics to load the root resource (image/js/css/etc. resources are not taken into account)

Reload of not existing page without UI (/xwiki/bin/get/NoSpace/NoPage)

Reload of not existing page with UI (/xwiki/bin/view/NoSpace/NoPage)

Reload of Main.WebHome with UI

Reload of Main.WebHome without UI

SOLR

Full SOLR reindex

• Delete the data/solr folder, restart, load home page and calculate the time of activity of the SOLR index thread using Yourkit
• Yourkit is slowing down a bit all that but what is important is the difference anyway

SOLR sync

• Only the thread determining what needs to be indexed and not the actual indexing

when index is empty

when there is nothing to do

Rendering

Page with 1000 macros without UI

• 1000 times {{id}} macro, one on each line

Memory

• Attach Yourkit to get the information

Memory after jetty startup

• Start jetty and wait until Java is not doing anything on both
• Wait for potential initialization of various stuff like core extension cache, etc

Memory after full SOLR index

• Delete the data/solr folder, restart, load home page then wait until nothing is happening in background