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

Eliza Weisman b6dbfdeee9 chore(docs): add Netlify docs builds 3 år sedan
.github 299011398b chore(ci): run the slowest loom models in separate jobs (#21) 3 år sedan
assets 853df894c2 docs: add benchmarks to readme 3 år sedan
bench 8c882b0f40 perf(mpsc): rewrite and optimize wait queue (#22) 3 år sedan
bin 974f51e02f chore(test): fix loom script not forwarding args 3 år sedan
src 8c882b0f40 perf(mpsc): rewrite and optimize wait queue (#22) 3 år sedan
tests d590f6d937 test(mpsc): tests for draining after tx closes (#12) 3 år sedan
.envrc 84b9ce7057 initial commit 3 år sedan
.gitignore 84b9ce7057 initial commit 3 år sedan
Cargo.toml 8c882b0f40 perf(mpsc): rewrite and optimize wait queue (#22) 3 år sedan
README.md 853df894c2 docs: add benchmarks to readme 3 år sedan
default.nix 84b9ce7057 initial commit 3 år sedan
netlify.toml b6dbfdeee9 chore(docs): add Netlify docs builds 3 år sedan
shell.nix 84b9ce7057 initial commit 3 år sedan

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".