Add a performance test that measures the time it takes Dapr to save data into a state store.

The important piece that is being tested is the processing that Dapr does before saving to the state store. This test should not benchmark the component itself.

For that purpose, a baseline test scenario would have an app that saves a 1kb payload to Redis, followed by a test app that uses Dapr to sav

Environment

• VerneMQ Version: 1.11.0
• OS: CentOS 8.0
• Erlang/OTP version (if building from source):
• VerneMQ configuration (vernemq.conf) or the changes from the default :
  listener.ssl.default = 0.0.0.0:8883
  listener.ssl.allowed_protocol_versions = 3,4,5
  listener.ssl.require_certificate = on
  mqtt_connect_timeout = 30000
• Cluster size/standalone:

Expected behaviour

Set

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients