Is PERFORMANCE_TESTS required for developing new storage plugin? #4594
-
Hi, everyone, I'm developing a new storage plugin for JanusGraph based Microsoft Azure Table. I find that there're some tests marked as "PERFORMANCE_TESTS" which is disabled by default. I want to understand the design purpose of these tests. Are they required to pass for a new storage plugin? And if there is any performance number of existing storage plugin to compare with? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I wouldn't say so for any type of tests. Every storage plugin, including the officially supported ones, has some tests disabled due to their nature. Of course it will be great to pass as many tests as possible.
No. We do have some performance numbers though - every commit on main branch has a regression testing report, e.g. this. Those benchmarks run on a GitHub Action container, which can be unstable, so the perf numbers are just a reference. |
Beta Was this translation helpful? Give feedback.
I wouldn't say so for any type of tests. Every storage plugin, including the officially supported ones, has some tests disabled due to their nature. Of course it will be great to pass as many tests as possible.
JanusGraphConcurrentTest
is likely the most valuable one among these labeled asPERFORMANCE_TESTS
.No. We do have some performance numbers though - every commit on main branch has a regression testing report, e.g. this. Those benchmarks run on a GitHub Action container, which can be unstable, so the perf numbers are just a reference.