Loadtest

Run helm charts individually

Loadtest

• Here nginx container & loadtest init-container with in single pod will get launch. In case if persistence is enabled in all the above helm charts, cleanDir is used to delete the directories inside /mnt/kubernetes after uninstalling the above helmcharts.

• Its replicas & block worker URL can be controlled by setting the values as mentioned in values.yaml.

• Never run the loadtest on the same server on which n/w is deployed. Run it on the separate server.

• Always create a new namespace in which you can run the loadtest. Example:

  kubectl create ns loadtest

• Example for its usage in single command, you must use the namespace according to your network name. Also other values can also be set according to requirements:-

  helm upgrade --install -n loadtest loadtest \
      --set loadtest.namespace=loadtest \
      --set loadtest.hostName=loadtest-network \
      --set loadtest.host=0chain.net \
      --set loadtest.config.serverChain.blockWorker=https://beta.0chain.net/dns \
      0chain-helm/loadtest

  It will create the url for report to get uploaded on https://loadtest-network.0chain.net/loadtest after loadtest completion. For loadtest logs please refer to its grafana & rancher.

• Note: By default persistence.enabled: false. It means it will use openebs to create pvc's. In case if it is true, it will create pv as well as pvc's.

• Note: While specifying the hostName & host in helm command it will create the ingress with the same URLs as created in DNS. Example: In beta.0chain.net hostName will be beta & host will be 0chain.net. Necessary Urls will automatically get replaced in various configs/deployment files, if it is specified correctly.