...
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:
...
| Code Block | ||
|---|---|---|
| ||
java -Xms40m -Xmx512m -XX:+HeapDumpOnOutOfMemoryError -XX:+UseConcMarkSweepGC -XstartOnFirstThread -jar plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.101.v20120109-1504 -console -clean -debug -nl en -data @noDefault -noExit -gcf /config/NEXMarkGeneratorConfiguration.properties -useNIO -pr 65440 -Dosgi.requiredJavaVersion=1.5 -Dorg.eclipse.swt.internal.carbon.smallFonts |
...
Optional: Configure Nexmark
...
- 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.
- Hints:
- 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!
- Hints:
- 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.
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd"> <properties> <!-- Konfiguration des NEXMarkGenerators --> <!-- Zeitangaben in MS --> <entry key="minDistBetweenPersons">5000</entry> <entry key="maxDistBetweenPersons">5000</entry> <entry key="minDistBetweenAuctions">2000</entry> <entry key="maxDistBetweenAuctions">2000</entry> <entry key="minDistBetweenBids">500</entry> <entry key="maxDistBetweenBids">500</entry> <!-- Faktor um den die Zeit beschleunigt werden soll. --> <entry key="accelerationFactor">1</entry> <!-- wie lange Auktionen offen bleiben sollen --> <entry key="minAuctionDuration">600000</entry> <entry key="maxAuctionDuration">600000</entry> <!-- Zeit zwischen zwei Bursts (MIN und MAX) in ms --> <!-- Ein Wert von 0 bei beiden simuliert ohne Bursts. --> <!-- Diese Zeit wird nicht vom "accelerationFactor" beeinflusst --> <entry key="minTimeBetweenBursts">0</entry> <entry key="maxTimeBetweenBursts">0</entry> <!-- Dauer eines Bursts --> <!-- Ein Wert von 0 bei beiden simuliert ohne Bursts. --> <!-- Diese Zeit wird nicht vom "accelerationFactor" beeinflusst --> <entry key="minBurstDuration">0</entry> <entry key="maxBurstDuration">0</entry> <!-- Beschleunigungsfaktor waehrend eines Bursts --> <entry key="burstAccelerationFactor">0</entry> </properties> |
...