Page History

...

docker pull odysseusol/nexmark
docker run  -d -p65440:65440 -p65441:65441 -p65442:65442 -p65443:65443 odysseusol/nexmark

#if you want to configure nexmark (Remark: Change YOURLOCALFOLDER with you folder e.g. "c:/volume/nexmark"
docker run  -d -v YOURLOCALFOLDER:/var/lib/nexmark -p65440:65440 -p65441:65441 -p65442:65442 -p65443:65443 odysseusol/nexmark

#if you want to run nexmark even after restarts and configure nexmark (Remark: Change YOURLOCALFOLDER with you folder e.g. "c:/volume/nexmark")
docker run  -d --restart unless-stopped -v YOURLOCALFOLDER:/var/lib/nexmark -p65440:65440 -p65441:65441 -p65442:65442 -p65443:65443 odysseusol/nexmark

...

You will see that the benchmark opens 4 servers on ports 65440 - 65443 where you can connect to.

Now Odysseus can use the nexmark sources. Each time an Odysseus query connects to one of the servers a new scenario is started, i.e. the same users and the same auctions are generated, so the same queries will always create the same results.The created events are consistent, e.g. there will be no bid for an auction that has not been created.

An alternative is to use the download version:

Go to http://odysseus.informatik.uni-oldenburg.de/download/nexmark/ and download a version that fits to your operatoring system (e.g. nexmark.win32.win32.x86_64.zip for a 64bit Windows).

...

Unzip the archive and start the "nexmark.exe" within the nexmark folder. This should look like in the following:

You may see that the benchmark opens 4 servers on ports 65440 - 65443 where you can connect to.

Now Odysseus can use the nexmark sources. Each time an Odysseus query connects to one of the servers a new scenario is started, i.e. the same users and the same auctions are generated, so the same queries will always create the same results.The created events are consistent, e.g. there will be no bid for an auction that has not been created.

Error Windows (10 or 11):

Remark: Especially, if there are multiple JDK installed, you could get an error like "No exit data available" and Nexmark does not start. This is typically because the wrong JDK is bound. In this case you could open the nexmark.ini File and add two lines bevore -vmargs (Change path to your jvm.dll location for Java 11)

-vm
C:/Program Files/Java/jdk-11.0.8/bin/server/jvm.dll

...

Configure Nexmark

Nexmark has some standard configuration that will be used in our examples.The configuration can be changed in nexmark.ini.

...

• pr: This is the starting port of the first server (Auction). The next servers (PERSON, BID, CATEGORY) will get the next 3 ports.
• gcf: This parameter references a file that describes the behaviour of the nexmark server, e.g. how long is the delay between different elements in the stream. We deliver two standard configurations that can be found in the plugin de.uniol.inf.is.odysseus.nexmark:
  • /config/NEXMarkGeneratorConfiguration_SLOW.properties: Here elements are delivered with a rather slow rate. This should be used when creating queries.
  • /config/NEXMarkGeneratorConfiguration.properties: Here elements are created with a higher rate. This can be used to test, if the application scales.
• useGlobalGenerator: If this flag is set Nexmark will start the simulation with the first access from any client and resumes the simulation until the program is stopped explicity.

Nexmark Configuration File

When using docker, you will need to bind a volume with -v (see example above)

In the following code block is an example of a nexmark configuration (/config/NEXMarkGeneratorConfiguration_SLOW.properties). All time elements are in milliseconds.

...