Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stress-test PVWS #29

Closed
3 tasks
rerpha opened this issue Aug 23, 2024 · 1 comment
Closed
3 tasks

stress-test PVWS #29

rerpha opened this issue Aug 23, 2024 · 1 comment

Comments

@rerpha
Copy link
Contributor

rerpha commented Aug 23, 2024

As a developer I would like to see how well PVWS deals with lots of subscriptions. This isn't really likely going to require any code changes in this repository.

we should see how PVWS reacts (pun intended) to:

  • subscribing to absolutely every single PV around isis
  • subscribing to the same PV 10000 times over different websockets - does it create a monitor for each?
  • subscribing to a large number (lets say 10M) of PVs that don't exist
This was referenced Sep 12, 2024
@rerpha
Copy link
Contributor Author

rerpha commented Sep 20, 2024

Given that:

  • PVWS makes one connection per PV, rather than per websocket
  • the CA gateway will likely be the bottleneck if there is one
  • we probably have less PVs than the ORNL usage

I am going to close this ticket as I believe it's superfluous.

@rerpha rerpha closed this as completed Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant