You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2020. It is now read-only.
We will need to have benchmarks with more than one node, so that we can benchmark things like exchange and pubsub. These multiple node tests will not make sense for profiling, so a good strategy to isolate them might be to have ./suite/benchmark/ and ./suite/profile/ for specific benchmark and profiling tests respectively and running any test found at ./suite/ in both lands (to avoid duplication of code).
A way that this could be done is by changing the benchmark suite signature to look like:
We will need to have benchmarks with more than one node, so that we can benchmark things like exchange and pubsub. These multiple node tests will not make sense for profiling, so a good strategy to isolate them might be to have
./suite/benchmark/
and./suite/profile/
for specificbenchmark
andprofiling
tests respectively and running any test found at./suite/
in both lands (to avoid duplication of code).A way that this could be done is by changing the benchmark suite signature to look like:
This way the node spawning would still remain independent from running the benchmark.
The text was updated successfully, but these errors were encountered: