I’d like to follow up on the comments I made earlier today at the community meeting around performance testing.  We are seeing potential users and customers starting to run such tests as they evaluate the software, and there are some known issues.  If we could address them, it might help turn potential users into users.

The performance tests that Victor and the team developed are partially open sourced.  I’m going to ask Nic to finish that work and contribute the tests to the Test project.

Meanwhile, our testing showed two issues where the performance of StarlingX is 10X or more worse than the original seed code.

One is captured in this bug [1].  The swact command is about 10X slower in R3 than in the seed code.  There is some good analysis in the LP.  The last comment in the bug is from Frank and says “Changed the priority to low and removed the stx.4.0 tag as this is not a functional issue and the changes required to improve performance require significant work more suited under a SB than a LP.”

So I’d like to ask – which sub-project should this work land?  What needs to be in the SB?  How can we move this forward?

The other issue is related to the test “time to detect a failed OpenStack VM”.  This is likely directly related to a patch that we no longer carry in StarlingX.  A version of that patch can be found here [2].

I don’t believe it’s worth our time to try (again) to push that patch.  It’s been rejected at least once.  The direction from the Nova community at the time was to (somehow) implement this functionality outside of Nova.  Which means we need a SB for it.  Do we know how to solve this problem?  What sub-project should that work land in?  How can we move this forward?

       brucej

[1] https://bugs.launchpad.net/starlingx/+bug/1838411

[2] https://gist.github.com/VictorRodriguez/e137a8cd87cf821f8076e9acc02ce195