Configurations
February 17, 2025About 2 min
There are some predefined configurations for the simulators and nodes.
Simulator configurations
There is a list for simulator configurations.
All these configurations have default values, usually you do not need to change them unless you have special requirements. They are in SimulatorConfigurator
class in the configurator
package. But we suggest you to modify them in our user interface.
Option | description |
---|---|
volumePath | The address where the TEQ file is mounted inside the container |
volumeFolderName | The external folder that will be mounted inside the container will contain all the resources that need to be used within the container |
startScriptName | The name of the script that will be executed when the container starts |
startPackageName | TEQ will generate a java package with this name to start the simulation process in docker containers |
startClassName | the starter class name in the starter package |
imageName | The name of the image that will be used to create the container, image provided by TEQ is recommended |
tcpPort | The port used to connet the docker daemon |
getStdout | when enabled, the stdout of the container will be printed to the console |
defaultLayerNamePrefix | the prefix of the layer name when you do not specify a name for a layer.(these layer whill be named as 'layer0', 'layer1', 'layer2', ...) |
metricsPort | All the containers will send their individual metrics to NetworkHost node at this port |
MetricsReceiverPort | The NetworkHost node will aggregate all the metrics and send them to the host(the main process) at this port.This means the inner docker network and the main process will communicate through this port |
restfulPort | The port used to send data to the front end(User Interface) |
classNamePrefix | All the container names will have this prefix to identify them |
cleanUpAfterSimulation | When enabled, the container will be removed after the simulation is finished |
displayInterval | The interval of the metrics transformation,the metrics will be transformed and sent to the front end every displayInterval milliseconds |
Nodes configurations
There is a list for node configurations.
All these configurations have default values, you can change them to simulate different scenarios in edge computing.They are in DockerNodeParameters
class in the node
package. But we suggest you to modify them in our user interface.
All the configurations will be applied in real time during the simulation.
Option | description |
---|---|
cpuUsageRate | percentage of the cpu usage rate, 0.5 means 50%, it can be larger than 1(means using more than 1 core) |
memorySize | unit: GB |
networkOutBandwidth | the bandwidth of the network out for this node, unit: kbps |
networkOutLatency | the latency of the network out for this node, unit: ms |
networkInBandwidth | unit: kbps |
networkInLatency | unit: ms |
fixedInLatency | when this is not 0, the network in latency will be fixed to this value, unit: ms |
fixedOutLatency | when this is not 0, the network out latency will be fixed to this value, unit: ms |