lfbb
Disruptor
lfbb | Disruptor | |
---|---|---|
10 | 30 | |
56 | 17,029 | |
- | 0.4% | |
6.2 | 5.4 | |
about 1 month ago | 4 months ago | |
C++ | Java | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lfbb
- A lock-free ring-buffer with contiguous reservations (2019)
-
OpenPicoRTOS: 'cause the world DEFINITELY needs another RTOS !
If you're interested in how to do that you can check out a library of mine: https://github.com/DNedic/lfbb (although you don't need to bother with memory ordering if you don't want, you can just use the sequential consistency model).
-
How do you handle data coupling between RTOS tasks?
You might be interested to take a look at this if efficiency is one of your goals: https://github.com/DNedic/lfbb
-
Library for generic ringbuffer that can be filled via DMA?
I have exactly what you are looking for https://github.com/DNedic/lfbb
-
Best practices on loosely coupling the high-level modules on a sensor-packager-transmitter embedded c device.
I don't see a reason SensorCollector should send a flag when there is enough data to send, the circular buffer object should be able to tell you when there is enough data to send and it should not be coupled to your specific applicaton. For situations where you want the data to always be contigous and need a general purpose circular buffer, you can take a look at a library i wrote: https://github.com/DNedic/lfbb
- LFBB – A Lock Free Bipartite Buffer Library Written in Standard C11
-
Best practice for preventing data collisions between ISR and non ISR code without turning off interrupts? (FreeRTOS)
If you need something more advanced, check this out: https://github.com/DNedic/lfbb
- A Lock Free Bipartite Buffer Library Written in Standard C11
- Lock Free Bipartite Buffer Library Written in Standard C11
- A Lock Free Bipartite Buffer library written in standard C11
Disruptor
-
Gnet is the fastest networking framework in Go
https://lmax-exchange.github.io/disruptor/#_what_is_the_disr.... Unfortunately IIUC writing this in Go still prevents the spin-locked acceptor thread from achieving the kind of performance you could get in a non-GC language, unless you chose to disable GC, so I'd guess Envoy is still faster.
https://gnet.host/docs/quickstart/ it's nice that you can use this simply though. Envoy is kind of tricky to setup with custom filters, so most of the time it's just a standalone binary.
[0] https://blog.envoyproxy.io/envoy-threading-model-a8d44b92231...
[1] https://lmax-exchange.github.io/disruptor/#_what_is_the_disr...
-
A lock-free ring-buffer with contiguous reservations (2019)
See also the Java LMAX Disruptor https://github.com/LMAX-Exchange/disruptor
I've built a similar lock-free ring buffer in C++11 https://github.com/posterior/loom/blob/master/doc/adapting.m...
-
JEP Draft: Deprecate Memory-Access Methods in Sun.misc.Unsafe for Removal
"Why we chose Java for our High-Frequency Trading application"
https://medium.com/@jadsarmo/why-we-chose-java-for-our-high-...
LMAX Disruptor customers
https://lmax-exchange.github.io/disruptor/
Among many other examples.
-
LMAX Disruptor – High Performance Inter-Thread Messaging Library
Current documentation
https://lmax-exchange.github.io/disruptor/
-
Progress on No-GIL CPython
LMAX Disruptor has on their wiki that average latency to send a message from one thread to another at 53 nanoseconds. For comparison a mutex is like 25 nanoseconds and more if Contended but a mutex is point to point synchronization.
The great thing about it is that multiple threads can receive the same message without much more effort.
https://github.com/LMAX-Exchange/disruptor/wiki/Performance-...
https://gist.github.com/rmacy/2879257
I am dreaming of language that is similar to Smalltalk that stays single threaded until it makes sense to parallise.
I am looking for problems to parallelism that are not big data. Parallelism is like adding more cars to the road rather than increasing the speed of the car. But what does a desktop or mobile user need to do locally that could take advantage of the mathematical power of a computer? I'm still searching.
- Disruptor 4.0.0 Released
-
Anything can be a message queue if you use it wrongly enough
Database config should be two connection strings, 1 for the admin user that creates the tables and anther for the queue user. Everything else should be stored in the database itself. Each queue should be in its own set of tables. Large blobs may or may not be referenced to an external file.
Shouldn't a message send be worst case a CAS. It really seems like all the work around garbage collection would have some use for in-memory high speed queues.
Are you familiar with the LMAX Disruptor? Is is a Java based cross thread messaging library used for day trading applications.
https://lmax-exchange.github.io/disruptor/
-
Any library you would like to recommend to others as it helps you a lot? For me, mapstruct is one of them. Hopefully I would hear some other nice libraries I never try.
Disruptor for inter-thread messaging
-
Measuring how much Rust's bounds checking actually costs
I have never worked in any industries where a perf margin was that small. It is funny, in HFT there are folks using Lmax (Java) and then you have folks writing their own TCP/IP stacks on FPGAs to do trading.
What are some alternatives?
lwrb - Lightweight generic ring buffer manager library
JCTools
nanoprintf - The smallest public printf implementation for its feature set.
Agrona - High Performance data structures and utility methods for Java
fifo_map - a FIFO-ordered associative container for C++
fastutil - fastutil extends the Java™ Collections Framework by providing type-specific maps, sets, lists and queues.
Vitis-Tutorials - Vitis In-Depth Tutorials
MPMCQueue.h - A bounded multi-producer multi-consumer concurrent queue written in C++11
muon - GPU based Electron on a diet
Eclipse Collections - Eclipse Collections is a collections framework for Java with optimized data structures and a rich, functional and fluent API.
OpenPicoRTOS - Very small, safe, lightning fast, yet portable preemptive RTOS with SMP support
Javolution