Performance test on Jetty/HSQLDB with a single wiki between 6.4.4 and 7.1
Environment
- Ubuntu 15.04 64b
- Quad core i7-3630QM
- Oracle JDK 1.8.0_45 64b
- standard jetty+hsqldb
- permdir in a SSD
- only main wiki
- configuration
- xwiki.cfg:
- xwiki.store.cache.capacity=500
- Admin user:
- hidden documents enabled
- xwiki.cfg:
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.) and logged in with Admin user. 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
Actions | Difference | |
---|---|---|
Jetty startup | similar | |
First access | not existing page without UI | similar |
not existing page with UI | 20% quicker | |
Reload | not existing page without UI | similar |
not existing page with UI | slightly better | |
Main.WebHome with UI | slightly better | |
Main.WebHome without UI | slightly better | |
SOLR | Full SOLR reindex | similar |
SOLR sync when index is empty | similar | |
SOLR sync when there is nothing to do | similar | |
Result of search finding lots of results | 30% quicker | |
Result of search finding one result | 20% quicker | |
Rendering | Page with 1000 macros without UI | /40 |
Page with 1000 html macros without UI | /8 |
Memory
Actions | Difference |
---|---|
Heap Memory after jetty startup | similar |
Heap Memory after full SOLR index | higher |
Jetty startup
Unit: seconds
Execute echo `date` && ./start_xwiki.sh and compare "Server started..." log date the one printed before jetty startup.
- 6.4.4: 8
- 7.1: 9
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).
- 6.4.4: 6
- 7.1: 6
First access to not existing page with UI (/xwiki/bin/view/NoSpace/NoPage)
Unit: seconds
Done by hand with a chronometer (image/js/css/etc. resources are not taken into account).
- 6.4.4: 15
- 7.1: 12
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
- 6.4.4: [7, 10]
- 7.1: [7, 10]
Reload of not existing page with UI (/xwiki/bin/view/NoSpace/NoPage)
Unit: milliseconds
- 6.4.4: [70, 90]
- 7.1: [60, 80]
Reload of Main.WebHome with UI
Unit: milliseconds
- 6.4.4: [155, 220]
- 7.1: [150, 200]
Reload of Main.WebHome without UI
Unit: milliseconds
- 6.4.4: [80, 110]
- 7.1: [70, 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).
- 6.4.4: 74
- 7.1: 70
SOLR sync
Only the thread determining what need to be indexed and not the actual indexing.
when index is empty
Unit: seconds
- 6.4.4: 1
- 7.1: 1
when there is nothing to do
Unit: seconds
- 6.4.4: < 1
- 7.1: < 1
Search
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).
Unit: milliseconds
Result of search finding lots of results
Login with Admin user and make sure hidden document display is enabled.
- 6.4.4: [350, 450]
- 7.1: [270, 290]
Result of search finding one result
- 6.4.4: [220, 250]
- 7.1: [160, 200]
Rendering
Page with 1000 macros without UI
.
Unit: milliseconds
- 6.4.4: 3000
- 7.1: 80
Page with 1000 html macros without UI
.
Unit: milliseconds
- 6.4.4: 6000
- 7.1: [750, 800]
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.
- 6.4.4: 45 used, 489 allocated
- 7.1: 40 used, 494 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
- 6.4.4: 108 used, 503 allocated
- 7.1: 144 used, 503 allocated