v6d
cpp-ipc
Our great sponsors
| v6d | cpp-ipc | |
|---|---|---|
| 5 | 1 | |
| 802 | 1,597 | |
| 1.6% | - | |
| 9.5 | 6.1 | |
| 8 days ago | about 2 months ago | |
| C++ | C++ | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
v6d
-
Has anyone here had experience using Vineyard?
Brief Overview for any interested: Vineyard (v6d) is an in-memory immutable data manager that provides out-of-the-box high-level abstraction and zero-copy in-memory sharing for distributed data in big data tasks, such as graph analytics (e.g., GraphScope), numerical computing (e.g., Mars), and machine learning.
-
GitHub “allows” unauthorized users “merging” PRs, bypass write permission check
- https://github.com/v6d-io/v6d/pull/948
-
[P] Bridging Dask and Tensorflow for distributed machine learniing with Vineyard
We propose vineyard, https://github.com/v6d-io/v6d to address such challenges, which, provides efficient zero-copy data sharing between different compute engines, without extra cost of copying and serialization, compared other similar solutions.
- Vineyard 0.2.7: Airflow, Dask, and better ML experience
- Vineyard v0.2.0: big-data applications optimization on Kubernetes
cpp-ipc
-
What are the "best practices" or "better design patterns" for posting message from one thread to others?
I'm working on a complex c++ project for my company these days. First, I need to pass 5 different types of messages (and attached data) from Process A to Process B. I use cpp-ipc and it works fine. And in Process B, there is one thread (called thread b) which is responsible for receiving those messages and "posting" them to other threads. I can't determine (and of course, don't know) the good solutions. My current idea is to use 5 concurrent queues for the 5 types of message. When thread b receives a message, it pushes the message to a queue, and other threads take the message from the queue. pseudocode example:
What are some alternatives?
shadesmar - Fast C++ IPC using shared memory
Osiris - Free and open-source game hack for Counter-Strike 2, written in modern C++. For Windows and Linux.
zef - Toolkit for graph-relational data across space and time
polybar-dwm-module - A dwm module for polybar
iceoryx - Eclipse iceoryx™ - true zero-copy inter-process-communication
GraphScope - 🔨 🍇 💻 🚀 GraphScope: A One-Stop Large-Scale Graph Computing System from Alibaba | 一站式图计算系统
filesystem - An implementation of C++17 std::filesystem for C++11 /C++14/C++17/C++20 on Windows, macOS, Linux and FreeBSD.
pe-util - List shared object dependencies of a portable executable (PE)
ecal - 📦 eCAL - enhanced Communication Abstraction Layer. A high performance publish-subscribe, client-server cross-plattform middleware.
ultimatepp - U++ is a C++ cross-platform rapid application development framework focused on programmer's productivity. It includes a set of libraries (GUI, SQL, Network etc.), and integrated development environment (TheIDE).