基于c++内存池,共享内存和信号量实现高速的进程间通信队列,单进程读单进程写无需加锁，多进程读多进程写用信号量集实现读写锁保证读写安全
active 2023-08-18 → 2026-05-03 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 990 days from 2023-08-18 to 2026-05-03. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 7 total, peak 2 in a day. Comments: 1 total, peak 1 in a day. Stars: 51 total, peak 2 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| panfeng5 | 5 | 0 | 0 | 0 |
| Sam-gsj | 1 | 0 | 0 | 0 |
| suyanye1213 | 1 | 0 | 0 | 0 |
| fanfanaaaa | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue#9panfeng52025-08-20 00:32单读单写没有加锁，会导致两个进程对m_iEnd和m_iBegin的读写存在竞争
- Issue#9panfeng52025-06-03 04:52单读单写没有加锁，会导致两个进程对m_iEnd和m_iBegin的读写存在竞争
- Issue#9panfeng52025-06-03 04:51单读单写没有加锁，会导致两个进程对m_iEnd和m_iBegin的读写存在竞争
- Issue#9panfeng52025-06-02 01:21单读单写没有加锁，会导致两个进程对m_iEnd和m_iBegin的读写存在竞争
- Issue#9panfeng52025-05-27 08:12单读单写没有加锁，会导致两个进程对m_iEnd和m_iBegin的读写存在竞争
- Issue#8suyanye12132024-06-25 02:01请问您在ubuntu32位系统上测试过吗？我测试发现有内存泄露。
- Issue#7Sam-gsj2024-06-23 02:52多进程有一点点问题
- Issue comment#5fanfanaaaa2024-03-17 11:481M不到的数据 耗时3000+毫秒正常吗
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 51 stars here means stars gained during the window, not the repo's star count.