Database Reference
In-Depth Information
a
J
. (Adam's
userId
is
adam001
; this user has been uniquely indexed and his node ID
happens to be
0
.)
You'll be using two different clients for your experiments: the first is simply the Unix curl
client, and the other is the java-rest-binding client. (You can find the curl scripts and JUnit
client test classes that we used for our timings as part of the provided source code.
Ap-
pendix B
provides instructions for running these.)
Table 10.4
provides a template for you to fill in your findings as you go along.
Table 10.4. Performance metrics log:template
Curl client
Java REST binding
Number of
server calls
made
Scenario
Description
Cold
Warm
Cold
Warm
1
Raw REST API
2
Cypher call
3
Server plugin
Unmanaged ex-
tension
4
• Time is stated in milliseconds.
• Timing for curl client is done using the bash time command.
• Timing for the Java REST binding done using Java (Spring) StopWatch.
• Cold = server first stopped then started before the first REST call was made.
• Warm = second call (same as previous) made directly after first without server restart.
Cold vs. warm timings
The first call (a cold call) made to the server includes the time required to perform one-off
bootstrapping, caching, and initialization processing, which may not be present for subse-
quent (warm) calls. This means that cold calls will almost always be slower, and may also
be slightly less predictable than warm calls. We will be providing you with both timings to
provide a full picture.
