Performance test on Jetty/HSQLDB with a single wiki between 5.4.6 and 6.4
Environment
- Ubuntu 14.10 64b
- Quad core i7
- Oracle JDK 1.8.0_25 64b
- standard jetty+hsqldb
- only main wiki
Unless specifically indicated otherwise all the test are executed with a fully initialized instance (core extensions don't run anymore, SOLR index is fully up to date, etc.). Basically except for a few special tests we are using an instance that already been started and run until the proc is flat for some time.
Summary
Speed
Memory
Actions | Difference |
---|---|
Memory after jetty startup | |
Memory after full SOLR index |
Jetty startup
Unit: seconds
Until end message is printed. Done by hand with a chronometer.
- 5.4.6: 10
- 6.4: 8
First access
First HTTP request after restarting Jetty.
First access to not existing page without UI (/xwiki/bin/get/NoSpace/NoPage)
Unit: seconds
Firefox network statistics to load the root resource (image/js/css/etc. resources are not taken into account).
- 5.4.6 : 8
- 6.4 : 9
First access to not existing page with UI (/xwiki/bin/view/NoSpace/NoPage)
Unit: seconds
Firefox network statistics to load the root resource (image/js/css/etc. resources are not taken into account).
- 5.4.6 : 9
Done by hand with a chronometer (image/js/css/etc. resources are not taken into account).
- 6.4 : 18
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)
Unit: milliseconds
- 5.4.6 : [10, 20]
- 6.4 : [10, 20]
Reload of not existing page with UI (/xwiki/bin/view/NoSpace/NoPage)
Unit: milliseconds
- 5.4.6 : [75, 130]
- 6.4 : [70, 100]
Reload of Main.WebHome with UI
Unit: milliseconds
- 5.4.6 : [170,300]
- 6.4 : [150,220]
Reload of Main.WebHome without UI
Unit: milliseconds
- 5.4.6 : [60, 100]
- 6.4 : [50, 80]
SOLR
Full SOLR reindex
Unit: seconds
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).
- 5.4.6 : 59
- 6.4 : 60
SOLR sync
Only the thread determining what need to be indexed and not the actual indexing.
when index is empty
Unit: seconds
- 5.4.6 : 1
- 6.4 : 1
when there is nothing to do
Unit: seconds
- 5.4.6 : < 1
- 6.4 : < 1
Rendering
Page with 1000 macros without UI
1000 times {{id}} macro, one on each line.
Unit: seconds
- 5.4.6 : 10
- 6.4 : 3
Heap Memory
Attach Yourkit to get the information.
Unit: MB
Heap 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). Force garbage collector before looking at the values.
- 5.4.6 : 60 used, 449 allocated
- 6.4 : 44 used, 460 allocated
Heap Memory after full SOLR index
Delete the data/solr folder, restart, load home page then wait until nothing is happening in background. Force garbage collector before looking at the values.
Unit: MB
- 5.4.6 : 117 used, 499 allocated
- 6.4 : 90 used, 493 allocated