Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Referring to the issue # 130, About plotting the delay and throughput differently for uplink and downlink #131

Open
spaul13 opened this issue Nov 9, 2018 · 0 comments

Comments

@spaul13
Copy link

spaul13 commented Nov 9, 2018

@keithw thanks for the detailed reply. Its really helpful. Inside the replay shell I have tried mm-link --meter-all option but still showing invalid argument error. Here is the snippet

[replay] sj@p:~/mahimahi$ mm-link --meter-all
Usage: mm-link UPLINK-TRACE DOWNLINK-TRACE [OPTION]... [COMMAND]

Options = --once
--uplink-log=FILENAME --downlink-log=FILENAME
--meter-uplink --meter-uplink-delay
--meter-downlink --meter-downlink-delay
--meter-all
--uplink-queue=QUEUE_TYPE --downlink-queue=QUEUE_TYPE
--uplink-queue-args=QUEUE_ARGS --downlink-queue-args=QUEUE_ARGS

  QUEUE_TYPE = infinite | droptail | drophead | codel | pie
  QUEUE_ARGS = "NAME=NUMBER[, NAME2=NUMBER2, ...]"
      (with NAME = bytes | packets | target | interval | qdelay_ref | max_burst)
          target, interval, qdelay_ref, max_burst are in milli-second

Died on std::runtime_error: invalid arguments

can u please help me telling where I am wrong. Inside the replay shell if I run ifconfig I can see all the contacted servers (virtually created apache servers).

One another query, how to log the HTTP uplink and downlink traffic differently into two different files using the record shell.

Any help will highly be appreciated. Thanks again...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant