DST Task: vac:dst:status:2025q1-status-go-evaluation:subscription-performance
Subscription performance - Chat protocol benchmarks link
Setup 1 (using discV5BootstrapNodes
/wakuNodes
and base image):
Deploy 1 service node A that will act as bootstrap.
Deploy 1 service node B that will act as store.
Deploy 4 relay nodes (Group C)
Deploy 5 light nodes (Group D)
Looks like C are not sending/receiving messages between themselves, but the service node is forwarding to 4 other nodes.
In group C:
:3333/statusgo/InitializeApplication
:3333/statusgo/CreateAccountAndLogin
:3333/statusgo/CallRPC
:3333/statusgo/CallRPC
:3333/statusgo/CallRPC
:3333/statusgo/CallRPC
in the node that created the community (index 0)
'error': {'code': -32000, 'message': 'sql: no rows in result set'}
In group D:
We follow the same steps that in point 5, but in step b, we change "wakuV2LightClient": False
to "wakuV2LightClient": True
When we reach step f, we obtain the following error:
'error': {'code': -32000, 'message': 'sql: no rows in result set'}
First node in group C (index 0) starts publishing messages with :3333/statusgo/CallRPC
When using the base image, either setting up the ENR in wakuNodes
or discV5BootstrapNodes
resolves in the same behaviour. The light nodes cannot join the community.
When using other version the in the fleet configuration, when the other nodes in group C are trying to join the community, we obtain:
{'code': -32000, 'message': 'store node is not available'}