15:01:24 #startmeeting vsperf weekly 15:01:24 Meeting started Wed May 25 15:01:24 2016 UTC. The chair is mtahhan. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:24 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:01:24 The meeting name has been set to 'vsperf_weekly' 15:03:36 #info Maryam Tahhan 15:34:51 #topic committers nominations 15:35:30 #info congrats to Christian, Bill, Martin and Sridhar on their promotion to vsperf committers 15:35:38 #topic Dev update 15:35:51 #info Yardstick ramp up still ongoing 15:36:08 #info working on installing yardstick 15:36:18 #topic Xena update 15:36:38 #info still looking to bottom out on the continuous pvp results 15:36:53 #action Maryam to run vfio test and post results to JIRA 15:37:28 #info Christian has some patches and fixes for bidirectional traffic to be pushed soon. 15:37:44 #topic spirent update 15:38:20 #action Sridhar to give a presentation next week on the proposed changes to results for RFC 2899 15:38:35 #topic Moongen integration 15:38:45 #info B2B tests working 15:39:08 #info Bill is doing some general cleanup and refactoring. 15:39:27 #info first patches to be pushed 1st week in June 15:40:09 Intel POD 3 is not ready, hardware was delayed in shipping and has arrived today. It will take a day or so to get the systems into the racks 15:40:16 #info Automated configuration/translation from vsperf params to Moongen params is now implemented also 15:40:25 Hi Jack 15:40:35 thanks. 15:41:09 yes, the shipping container was damaged in shipping so hopefully systems as ok 15:41:10 jmorgan1: Can I ask that node 5 is prioritized so I can setup a sandbox for vsperf there 15:41:30 eek, fingers crossed 15:41:33 mtahhan: sure, but there is no task for me. correct? 15:42:04 :) I assumed the platform was getting swapped out of the POD for the new one. 15:42:18 ah, right. i'll take care of it first 15:42:31 once the physical platform is there I can do the rest :D 15:42:35 thanks a million 15:42:37 :D 15:42:41 mtahhan: no worries 15:42:53 excellent 15:43:10 #topic back to back testing 15:44:23 #action Maryam to collate results for back to back tests from the nightly build so we can see how consistent the results are 15:46:13 #info question, should the back to back test start at line rate for a particular time, maintain the minimum interframe gap and if there's packetloss, modify/reduce the rate run for the same period of time till the back to back value is found 15:47:09 #info that's one way of doing it. B2B test could also start at a low rate and work up. Or could be a binary search... 15:47:30 #info issues with the binary search in our current world... 15:47:48 #info TBD after we look at results next week 15:48:08 #action Maryam to follow up with David McBride on code freeze date 15:48:13 #endmeeting