Nexmark simulates an online auction setting and was originally designed as an benchmark for the Niagara streaming system (see http://datalab.cs.pdx.edu/niagara/NEXMark/).
In this scenario there are three streams Person, Auction and Bid and stored information (Category). At every time, new users can register themself in the system and create new auctions. Each user can also generate bids for auction. The Schema can be found in the picture above.
As default: Each time a client connects new (to one of the four streams) a new simulation is started (with reproducable data). To get consisten data, connections to the other three streams, will use the same simulation. So e.g., if you connect to a person stream and have no other connections to the server, the simulation start from the beginning. If you connect to another stream, e.g., bid, and you are still connected to the person stream, the bid stream fits to the person stream. If you connect to the bid stream after you disconnected from the person stream, a new simulation will be started. This behavior can be changed with an start up optoin.
We adapted this scenario for Odysseus and allow to configure the scenario.
Get and Start Nexmark Generator
We recommend using the docker version. Here all depedencies are already provided inside the docker-image
You could download nexmark from dockerhub (for windows and macos you could use the Docker Desktop):
Remark: If you want to configure in docker environments you could use the example files from: https://odysseus.informatik.uni-oldenburg.de/download/nexmark/config/. Only the file named NEXMarkGeneratorConfiguration.properties will be used. So change the name or adapt the file if you want to use the SLOW version.
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).
Nexmark needs at least Java 11.
Unzip the archive and start the "nexmark.exe" within the nexmark folder. This should look like in the following:
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)
Nexmark has some standard configuration that will be used in our examples.The configuration can be changed in
The following parameters can be adapted:
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
/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.
The following elements can be used:
- minDistBetweenPersons: How much time must pass, before a new person event can be created.
- maxDistBetweenPersons: What is the maximum time that is allowed to pass, before a new person is created.
- max must be higher or equal than min
- if max == min this is the rate at which the elements are created, else there will be a random value between min and max.
- the values are application time, e.g. the events will get a time stamp corresponding to the min/max value. This could be different from system time values!
- min/maxDistBetweenAuctions/Bids: The same as above, but for auctions and bids.
- acceleratorFactor: Typically, application time and system time are the same.So if there is 5 seconds defined as waiting time, there will be created elements each 5 seconds in real time (if the server is capable to, but this should be no problem with 5 seconds ). To get the same application time stamp but speed up processing, this parameter can be used.
- min/maxAuctionDuration: Each auction has a time at which bids can be posed. This values give the min and the max value, that will be used for each auction.
- min/maxTimeBetweenBursts: To allow times with higher data rates (more elements are send), bursts can be used. This value give the min and max waiting time between bursts. This value will not use acceleratorFactor, because it realtime and not applicationtime specific
- min/maxBurstDuration: How long will bursts takes.
- burstAccelationFactor: How many more elements will be send, during a burst phase.