3 ms·
We updated the title from “Memory Mapping 15x faster than Named Pipes and 2x faster than Queue (Java)“, which was referring to these benchmarks from the project
by sctb 10y ago
We updated the title from “Memory Mapping 15x faster than Named Pipes and 2x faster than Queue (Java)“, which was referring to these benchmarks from the project page:
ArrayDeque (synced) Records: 127.26/ms in 78579 ms => ~50% slower than Named Pipes
Named Pipes on TMPFS Records: 263.80/ms in 37908 ms => why ~5% slower on TMPFS?
Named Pipes Records: 281.15/ms in 35568 ms => using this as baseline
SynchronousQueue (fair) Records: 924.90/ms in 10812 ms => ~3 times faster than Named Pipes
LinkedBlockingQueue Records: 1988.47/ms in 5029 ms => ~7 times faster than Named Pipes
Mapped Memory Records: 3214.40/ms in 3111 ms => ~11 times faster than Named Pipes
Mapped Memory on TMPFS Records: 4237.29/ms in 2360 ms => ~15 times faster than Named Pipes
- gsubes 10y agowhy these title changes?!? Does one really have to write separate blog posts with the same title so they don't get changed?
- sctb 10y agoFrom the guidelines: > Otherwise please use the original title, unless it is misleading or linkbait. The long-standing policy is to represent the submitted content as accurately as possible and let readers pick out what's interesting to them, not what the submitter found interesting. A comment in the thread is a fine place to call such things out if a blog post is overkill.