2016-06-08 15:56, Kantecki, Tomasz: > Hi Thomas, > > > > 12s is long for a functional test. We are used to have tests of less than > > > 1s. > > > Do you think this magnitude order can be achieved for red tests? > > > > This is a real challenge :) Let me take another look into it. > > I had a 2nd look into this test suite and reducing time for functional tests > is doable but labor intensive. Let me explain: > RED/WRED algorithm is time based (packet queue events in time). For tracking > time the test uses TSC (x86 time stamp counter). This could be replaced with > some fake time stamp in functional tests and result in significant reduction > of execution time. It needs couple of days to carefully replace TSC with a > fake time stamp solution without breaking test logic.
Sorry, I haven't dived into the code, but I don't understand how we get some seconds delays in a code for fast processing on nano-second CPU. Are you sure you cannot have the same result with less iterations and shorter timeouts?
