imbajin opened a new issue, #355:
URL: https://github.com/apache/hugegraph-computer/issues/355
## Goal
Explore an **incremental Rust implementation** for selected graph-computing
components in HugeGraph Computer and Vermeer, focusing on kernels, data
movement, memory efficiency, and operational simplicity where Rust offers a
measurable advantage.
This is a parent tracking issue, not a commitment to replace the existing
Java/Go systems wholesale. Existing algorithms, formats, and deployments
remain
the compatibility and performance baseline.
## Proposed priority
This work follows the shared Toolchain and Server foundations. Within this
repository:
1. Establish representative graph datasets, algorithm outputs, and
performance
baselines for Computer and Vermeer.
2. Prototype a small isolated kernel or I/O component with a stable boundary.
3. Validate multi-worker behavior, determinism, failure recovery, and
resource
use before expanding scope.
4. Consider broader Vermeer/OLAP migration only after the experiments show a
clear maintenance and performance benefit.
## Delivery model
```text
baseline -> proposal/RFC -> isolated kernel or I/O slice
-> result-parity + scale tests -> opt-in preview -> staged adoption
```
Each child issue should define:
- scope, owner/mentor, and non-goals;
- input/output, algorithm, CLI/config, and deployment compatibility;
- result parity/tolerance, determinism, multi-worker, and recovery tests;
- reproducible throughput, memory, scaling, and cost benchmarks;
- security/dependency checks and supported platforms;
- coexistence, migration, and rollback plans;
- user and contributor documentation.
No large rewrite PR should start before its design and acceptance criteria
are
reviewed. Benchmark results must include datasets, hardware, configuration,
and
the current implementation used as the baseline.
## Candidate work items
- [ ] Define representative datasets and algorithm correctness fixtures
- [ ] Publish Computer and Vermeer performance/resource baselines
- [ ] Select one small proof-of-concept kernel or I/O path
- [ ] Decide the interoperability and packaging boundary
- [ ] Establish Rust CI, lint, dependency, and release conventions
- [ ] Validate local and multi-worker deployment paths
- [ ] Split approved work into newcomer-friendly child issues
This checklist will link to concrete child issues as proposals are accepted.
## Project-wide roadmap
Related parent issues will be linked here after creation.
## How to participate
Contributors interested in **open source, Rust, graph algorithms, distributed
computing, performance engineering, or infrastructure** are very welcome.
Please comment with the area you want to work on and any relevant experience.
Algorithms, benchmark datasets, correctness tests, deployment work, and
documentation are all useful entry points.
For first-time contributors, see the
[HugeGraph contribution
guide](https://hugegraph.apache.org/docs/contribution-guidelines/contribute/)
and the repository's `good first issue` / `help wanted` tasks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
