On Wed, Jul 1, 2015 at 3:17 PM, Ben Pfaff <b...@nicira.com> wrote: > On Wed, Jul 01, 2015 at 10:19:29AM +0000, Gray, Mark D wrote: >> > I would like to highlight the release of a new version of TOIT to the >> > vSwitch >> > Characterization project in OPNFV. >> > >> A tool like this could help ensure that there is no unexpected degradation >> in performance. Perhaps it could be used to gate patches to prevent >> performance >> drops of the type that Jesse's patch fixed this morning? > > It would be very useful to have a service that builds OVS DPDK, tests > its performance, and reports it. It could be a nightly build kind of > service, or it could be more like travis where it automatically tests > every OVS commit (even proposed ones) pushed to github. It would be a > real service to the community for Intel (or someone else) to set up > something like this.
It would definitely be great to have infrastructure to automatically test proposed patches for correctness and performance. I think this is one thing that Gerrit does very well, particular as we add more environments like DPDK and Windows that most developers might not be setup to test. I guess it seems particularly nice to have something that is both consistent (rather than having a mixture of different systems such as email, Travis, performance, Patchwork) and gating for commits, otherwise it will probably end up breaking at some point and being ignored. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
