镜像自: https://github.com/DragonOS-Community/thingbuf.git

Eliza Weisman 738191d77d chore(test): pin loom to a SHA 3 vuotta sitten
.github 299011398b chore(ci): run the slowest loom models in separate jobs (#21) 3 vuotta sitten
assets 853df894c2 docs: add benchmarks to readme 3 vuotta sitten
bench 8342ee9823 test(bench): remove `Throughput` from MPSC benchmarks 3 vuotta sitten
bin 974f51e02f chore(test): fix loom script not forwarding args 3 vuotta sitten
src c58c620096 fix(mpsc): fix a deadlock in async send_ref (#20) 3 vuotta sitten
tests d590f6d937 test(mpsc): tests for draining after tx closes (#12) 3 vuotta sitten
.envrc 84b9ce7057 initial commit 3 vuotta sitten
.gitignore 84b9ce7057 initial commit 3 vuotta sitten
Cargo.toml 738191d77d chore(test): pin loom to a SHA 3 vuotta sitten
README.md 853df894c2 docs: add benchmarks to readme 3 vuotta sitten
default.nix 84b9ce7057 initial commit 3 vuotta sitten
shell.nix 84b9ce7057 initial commit 3 vuotta sitten

README.md

Is it fast?

Yes, it's fast

FAQs

  • Q: Why did you make this?

A: For tracing, I wanted to be able to send formatted log lines to a dedicated worker thread that writes them to a file. Right now, we do this using crossbeam-channel. However, this has the sad disadvantage that we have to allocate Strings, send them through the channel to the writer, and immediately drop them. It would be nice to do this while reusing those allocations. Thus...StringBuf.

  • Q: Is it lock-free?

A: Extremely.

  • Q: Is it wait-free?

A: As long as you don't use the APIs that wait :)

  • Q: Why is there only a bounded variant?

A: Because unbounded queues are of the Devil.

  • Q: Isn't this just a giant memory leak?

A: If you use it wrong, yes.

  • Q: Why is it called that?

A: Originally, I imagined it as a kind of ring buffer, so (as a pun on "ringbuf"), I called it "stringbuf". Then, I realized you could do this with more than just strings. In fact, it can be generalized to arbitrary...things. So, "thingbuf".