Testing Environments

This page documents the various builds and parts that make up the environment of the published timing tests. It will be updated as these components change and improve. The timing tests results will always refer to their current environment version.

Environment A v1.1

Database

• Titan 0.3.?
• Built from the fabric-sie branch
• This branch is currently necessary to build against the latest Blueprints
• Using local Berkeley DB
• TinkerPop 2.4.0-SNAPSHOT stack
• Running on a MacBook Pro
• Connected to local network via ethernet
• Average latency between client machine and database server: 1ms

Pinging 192.168.1.115 with 32 bytes of data:
Reply from 192.168.1.115: bytes=32 time=1ms TTL=64
Reply from 192.168.1.115: bytes=32 time=1ms TTL=64
Reply from 192.168.1.115: bytes=32 time=1ms TTL=64
Reply from 192.168.1.115: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.115:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms

Client

• Timing code is executed as unit tests
• Compiled in "Release" mode
• Running within ReSharper's "Unit Test Sessions" window
• Warm ups, rounds, and round sizes:
• Each method has several unrecorded "warm up" executions
• Each test runs several "rounds"
• Each method's executions run sequentially within a "round"
• For example:
  • 5 warm up executions for each method
  • 10 rounds
  • In each round, loop through the various methods
  • Run 100 serial/parallel executions for each method
  • Each method gets a total of 1,000 recorded executions
• Parallel tests execute with max degree of parallelism of 8
• This is equal to the number of cores on the client computer

RexConnect

• RexConnect 0.4.0
• Installed in "Rexster Extension" mode (running in the same JVM as Titan)
• Uses RexPro's MsgPack messaging format internally
• RexConnectClient 0.4.0.1

RexPro Client

• RexPro-Client 1.?
• Built from the rexpro-v1 branch
• This branch is currently necessary to use the new RexPro JSON messaging

Environment B

The same as Environment A, except:

Client

• The same machine as the database server
• Uses the Mono framework instead of .NET
• Running within MonoDevelop's unit test runner
• Connects via 127.0.0.1 instead of local network