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

performance testing of GB and GC #110

Open
tomkralidis opened this issue Sep 12, 2023 · 1 comment
Open

performance testing of GB and GC #110

tomkralidis opened this issue Sep 12, 2023 · 1 comment

Comments

@tomkralidis
Copy link
Collaborator

Given various discussions on WTH, it would be valuable to put forth a testbed / experiment help measure performance of GBs and GCs with:

  • deep topic levels
  • large data files
  • multiple MQTT publishers/subscribers/downloaders

cc @golfvert @kaiwirt @Haddouch101 @hhaddouch @efucile

@golfvert
Copy link
Contributor

We are planned (almost agreed) to have hackathon week(s) next year to stress the system.
For that, we would need to define the scenario.

  • Topic level depth is not an issue (up to a reasonable limit ~50 and we are far from it)
  • Large files we already have the cache / no cache option. Do we need more ? Typically if a WIS2 Node proposes a large file ( what large is ?) then the GC MAY decide not to cache it ?
  • Multiple MQTT: what is "multiple" ? 100s 1000's More ?

I would be more interesting in checking the reliability, the redundancy of the design.

There are also existing stress test of MQTT brokers.

Last but not least, we have only ONE publisher for a WIS2 Node and we have (in Météo-France design) one publisher per WIS2 Node. So, in any case, the number is small.

@6a6d74 6a6d74 moved this to Uncategorized in WIS2 - the everything list Oct 6, 2023
@golfvert golfvert moved this from Uncategorized to For performance testing hackathon (2024Q2-Q3) in WIS2 - the everything list Oct 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: For performance testing hackathon (2024Q2-Q3)
Development

No branches or pull requests

2 participants