Hello Jonathan,

We have updated all the graphs with updated COBALT code and BQL enabled.

Wiki Link:
https://github.com/Daipu/COBALT/wiki

Diff for COBALT code:
https://github.com/Daipu/COBALT/commit/624d0c761b9d1de99499918cb2078195f8b796b5

Thanks and Regards,
Shefali Gupta
Jendaipou Palmei

On Wed 23 Jan 2019, 10:57 p.m. Shefali Gupta <shefaligups11@gmail.com wrote:
Hi Jonathan,

Thanks!

First, we noticed that cobalt_cache_init method was not implemented in ns-3 COBALT, so we implemented it (but this wasn't the main reason for the wrong behaviour).

Later, we found that the data types used in the implementation of COBALT in ns-3  were different from those used in Linux.

e.g., uint32_t was used instead of int64_t for the variables with datatype ktime_t in Linux.

Results improved considerably after these changes.

We will update the wiki with latest results.

Regards,
Shefali Gupta
Jendaipou Palmei

On Wed 23 Jan 2019, 9:53 p.m. Jonathan Morton <chromatix99@gmail.com wrote:
> On 23 Jan, 2019, at 6:19 pm, Shefali Gupta <shefaligups11@gmail.com> wrote:
>
> We believe we have spotted the issue now. The new plot is attached below.

That does look considerably improved.  What was the problem in the end?

Now would be a good time to regenerate all the test graphs, and make sure there are results for each test for each qdisc tested.  Ideally all graphs should be generated from the same run(s), to ensure their data is mutually consistent.

 - Jonathan Morton