Gruvi Alternatives

Similar projects and alternatives to gruvi

llvm-project

350 25,563 10.0 C++ gruvi VS llvm-project

The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
context

3 280 5.7 Assembly gruvi VS context
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
marl

1 1,781 5.7 C++ gruvi VS marl

A hybrid thread / fiber task scheduler written in C++ 11
stack-switching

2 102 10.0 WebAssembly gruvi VS stack-switching

A repository for the stack switching proposal.
assembly

4 15 9.5 C gruvi VS assembly

assembly projects (by samsquire)
cgreenlet

1 81 10.0 C gruvi VS cgreenlet

Coroutines for C/C++
ghost-userspace

2 207 8.1 C gruvi VS ghost-userspace
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better gruvi alternative or higher similarity.

Suggest an alternative to gruvi

gruvi reviews and mentions

Posts with mentions or reviews of gruvi. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-24.

Fiber in C++: Understanding the Basics
8 projects | news.ycombinator.com | 24 Sep 2023

A disadvantage to the ‘no function coloring’ in fibers is that it makes lockless programming harder. A nested function call can switch from under you without your knowledge, making it hard to know where the preemption points are and whether to take locks when making updates to shared state. With function coloring you know exactly whether a function might switch or not.
I’ve programmed both fiber based systems and coroutines. I even created my own fiber libraries for Python (https://github.com/geertj/gruvi) and C++ (https://github.com/geertj/cgreenlet, mostly an experiment, and incorrectly named coroutines for C++ while it’s really fibers). In the Python version I experimented with some features to help you know whether a nested function might switch.
In the end, for me and for the problem domains I worked in, the explicit async/await co-routine style wins over fibers. It gives you most of the performance and memory benefits of user mode switching while keeping your code mostly lock free.