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

A paragraph about networks and queue theory? #249

Open
dtaht opened this issue Jan 18, 2023 · 1 comment
Open

A paragraph about networks and queue theory? #249

dtaht opened this issue Jan 18, 2023 · 1 comment

Comments

@dtaht
Copy link

dtaht commented Jan 18, 2023

I was so glad to see you cite queue theory in your readme. I have written in many places about queue theory in general, as to how it applies to networks.

In particular, a treatment of "little's law" needs to done with great caution, as shedding load on networks is different than balancing load for disks, and I've always longed for more folk to have read Kathie Nichols & Van Jacobson's great paper on the codel algorithm here: https://queue.acm.org/detail.cfm?id=2209336 - or read up on fq_codel, which is usually the default network queuing algorithm in Linux nowadays.

Over here, last year, was a rollicking debate between Len Kleinrock (Father of modern queue theory) and Dave Reed (author of the end to end argument and creator of UDP) about how to think about little's law on networks: https://lists.bufferbloat.net/pipermail/cake/2021-July/005540.html

especially about the flaws in little's law - yet several folk in that discussion held on doggedly to their belief system. As much as I think more and more knowledge of how queues work is propagating to the SRE's and as much as I love flame graphs... in terms of trying to add a paragraph onto your stuff, I find that I do not know what y'all don't already understand?

PS: I only discovered your flamegraph tool today (I'd been using greggs work for years). It's awesome!

@djc
Copy link
Contributor

djc commented Jan 18, 2023

Hey, glad you're liking this tool! I'm a replacement maintainer for this tool, and am much less experienced/opinionated in terms of those sections of the README than the original maintainer (@spacejam) -- after all, in the end this tool just calls out to perf (or other supported sampling profilers on other platforms) and the inferno Rust library, so in that sense it doesn't really require in-depth knowledge to maintain.

I'm not also not super clear on what you're suggesting/requesting with this issue, but if you have some useful stuff to add, please feel free to submit a PR.

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