SebastianGruza commented on issue #3110: URL: https://github.com/apache/hugegraph/issues/3110#issuecomment-5751608769
I'll take the two checklist items that sit before HStore and PD in the gate order: **representative OLTP and storage workload baselines** and **rolling-upgrade and rollback requirements before HStore/PD work**. No overlap with #3145: codec fixtures and the PoC matrix stay there; I supply the numbers and the requirements that matrix asks for in its "oracle" and "fallback cost" columns for the storage layer. The material already exists, it is just scattered: over the last two weeks I measured on a 3-node cluster (chart from hugegraph/hugegraph#221) a Server rolling upgrade under load in three passes, PD behaviour after its disk fills up (#3222), the Store memory profile under the cluster preset, and readiness (#3221), always with an oracle checking that no acknowledged write was lost. The child issue below turns that into a repeatable set: one data generator shared with apache/hugegraph-toolchain#772 (there the loader is measured as a client, here the server and the storage), a fixed OLTP mix, HStore storage metrics, and written upgrade/rollback requirements with a harness that checks them. All Java and scripts, no Rust; it is the reference point without which no HStore or PD PoC has anything to compare against. Child issue with scope, non-goals and acceptance criteria: #3223. -- 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]
