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

Some question about simulation(about fluid model) #9

Open
btlcmr0702 opened this issue Apr 18, 2017 · 2 comments
Open

Some question about simulation(about fluid model) #9

btlcmr0702 opened this issue Apr 18, 2017 · 2 comments

Comments

@btlcmr0702
Copy link

hi, yi bo
I try to use ns3 to verfiy the fluid model you come up in 'Congestion Control for Large-Scale RDMA
Deployments
'.
Then i get some strange performance.
For example, i change parameter BYTE_COUNTER to 10MB which comes from your paper, but the rate of host can't converge and queue length at bottleneck varies a lot. Then i found some parameters that i don't understand:
CLAMP_TARGET_RATE
CLAMP_TARGET_RATE_AFTER_TIMER
If i set them both to 0, the rate of host can converge but it and queue length at bottleneck still oscillate a lot.
I stick the figure of performance(2 flow) as below.

i cyni_haz 1_bg 242ab

Thank you!

@bobzhuyb
Copy link
Owner

If you are referring to the straight, stable lines in the paper, they are the results of fluid model analysis.

The NS-3 simulation is packet-level. The random marking on switches can't keep the queue as stable as fluid model analysis. As long as your throughput is ~99% link rate and the queue length is mostly ~100KB or less, it is good enough in practice.

@btlcmr0702
Copy link
Author

btlcmr0702 commented Apr 18, 2017

Ok, thank for your reply.
But i still wonder what does these parameter used to? They are in file Qbb-net-device.cc/h
CLAMP_TARGET_RATE
CLAMP_TARGET_RATE_AFTER_TIMER

Will they affect performance a lot?

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

2 participants