The Request Log Parser processes raw Dgraph logs into properly formatted input for Eneperf.

Eneperf is a performance debugging tool that can measure throughput to help you identify system bottlenecks. Eneperf drives a substantial load at the MDEX Engine and reveals how many operations per second the MDEX Engine responds with. You specify a log file as input and tell Eneperf how many times to run through it, as well as the number of client connections to simulate.

Eneperf is an executable that is included in the MDEX Engine package. It is located at $ENDECA_MDEX_ROOT/bin/eneperf (UNIX) and %ENDECA_MDEX_ROOT%\bin\eneperf.exe (Windows).

A Dgraph process (version 5.1) generates request logs in the following format:

1146617085 10.0.18.19 – - 15805 15.66 2.49 200 5000 0 - /graph?node=0

But as input, the Endeca IAP 5.1 version of Eneperf requires a single log file with URL-only entries in the following format:

/graph?node=0

MDEX Engine 6.x request log entries include two additional fields after this URL, for post body and HTTP headers. These do not appear in dgraph logs from earlier versions. The Request Log Parser will retain these additional fields when processing 6.x request log entries, as they are used by 6.x versions of Eneperf.

The following is an example of how the Request Log Parser can be used in conjunction with Eneperf to replay two separate dgraph.log files against an index running on 10.0.0.1:8000. In this example, the log file will be replayed ten times using a five simultaneous connection.

reqlogparser dgraph1.log dgraph2.log > dgraph_parsed.log
eneperf 10.0.0.1 8000 dgraph_parsed.log 5 10