Yay, progress! ;)
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/144#issuecomment-406422670___
Flent-users mailing list
Flent-users@flent.org
thx! the network behavior I'm looking at itself doesn't make any sense, but at
least I can plot it now.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
Closed #144 via 27498cd7f10f765f55bc51971b3125ac0c454db0.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/144#event-1743371469___
Flent-users mailing list
the *weird* thing I'm actually trying to look at is that it takes 10sec for the
impact of the 10 new flows to truly hit, then all the other flows come back
hard, then 10 sec later, we achieve balance. I've been lying down on the job by
not thoroughly auditing the last 6 months worth of AQM
Nope; what you're seeing is actually an improvement; it is now partially
applying the absolute-time parameter, instead of not applying it at all ;)
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
and ok, I got around to installing pyqt5 and it does the same thing. Older
matplotlib?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
d@dancer:~/ne
![fortoke](https://user-images.githubusercontent.com/108682/42965417-c9dfa524-8b4e-11e8-8cc3-ffea1c1cd26e.png)
m$ flent-gui --absolute-time *500*.gz
Started Flent 1.2.2-git-09e66b3 using Python 3.5.2.
WARNING: Falling back to Qt4 for the GUI. Please consider installing PyQt5.
Dave Täht writes:
> i pulled. that fix breaks those plots completely in the general case.
Whaddyamean breaks plots completely? Looks fine on my machine...
-Toke
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
(I have no idea how you are holding cake, iproute2, and flent all in your head)
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/144#issuecomment-406384877___
Reopened #144.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/144#event-1743330633___
Flent-users mailing list
Flent-users@flent.org
i pulled. that fix breaks those plots completely in the general case.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/144#issuecomment-406384387___
Flent-users
Closed #144 via a1ba52e83b29ac6e55bce91e331feccd2e360878.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/144#event-1743324720___
Flent-users mailing list
Hmm, turns out there was a bug in the absolute_time handling :)
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/144#issuecomment-406383184___
Flent-users mailing
[tcp_nup-2018-07-19T114126.321412.500mbit-spaceheater-dancer-offset-20sec-ethernet.flent.gz](https://github.com/tohojo/flent/files/2211294/tcp_nup-2018-07-19T114126.321412.500mbit-spaceheater-dancer-offset-20sec-ethernet.flent.gz)
yes.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/144#issuecomment-406375455___
Flent-users mailing list
Flent-users@flent.org
15 matches
Mail list logo