docs(profile): parity & benchmarks evidence (streaming + databases)#12
Open
estebanzimanyi wants to merge 22 commits into
Open
docs(profile): parity & benchmarks evidence (streaming + databases)#12estebanzimanyi wants to merge 22 commits into
estebanzimanyi wants to merge 22 commits into
Conversation
A profile-linked, user-facing assessment of the streaming layer (MobilityFlink / MobilityKafka / MobilityNebula) as evidence the ecosystem is ready for real-world deployment — measured, not asserted: - function-surface coverage of the 1,945 streamable MEOS functions (Flink/Kafka 100% proven-callable; Nebula in progress, compile-verified), - BerlinMOD query-result parity (snapshot = batch), - the BerlinMOD performance benchmark (results published as clean runs complete). All coverage numbers are reproducible from committed feeds with no toolchain. Adds a "Parity & benchmarks" section to the profile README linking this page and its peer, "Databases — parity & benchmarks" (delivered separately).
…ing) Consolidates the database-layer evidence into a uniform page mirroring the streaming one: function-surface coverage (MobilityDB reference; MobilityDuck 943/943 active; MobilitySpark 1571/1577 + 29/29 portable dialect), the cross-type axis + reason-marked semantic exclusions, BerlinMOD query-result parity (discussion #861) and the cross-platform benchmark (MobilityDB-BerlinMOD #29). Numbers are sourced from the per-repo audits and advance as the accumulated-PR builds and dated runs land. Resolves the README "Databases — parity & benchmarks" link added in this PR.
estebanzimanyi
changed the title
…-click depth) Per the chosen layout: each page now opens with a coverage bar chart from the real measured numbers, a correctness + benchmark status line, and a 'Full results & raw data' block linking the per-repo audits and benchmark report #29. Incomplete parts (Nebula 7.6%, benchmark dated runs) are shown honestly.
…maid) Replace the placeholder unicode bars with real coverage charts generated by profile/images/coverage_charts.py — same approach as the BerlinMOD benchmark's chart.py (matplotlib -> committed PNG, embedded via <img> with the canonical main raw URL + ?v= cache-bust, matching the ecosystem SVG figure). Solid bar = proven/reference, hatched = wired-not-yet-proven. Reproducible: re-run the script after the numbers change.
…-promissory (a) Correctness is now backed, not asserted: 27/27 BerlinMOD-9 x 3-form cells reproduce the batch result per platform; Flink snapshot is byte-identical. Remove the 'dated runs publishing' / 'advances as families wired' future-tense framing; the benchmark line states the in-place methodology, and the status footer states present measured fact (Flink/Kafka 100%, Nebula as wired to date).
…on ops) Regenerate streaming-coverage.png at the new measured number, bump the image cache-bust to ?v=2, and update the alt text + coverage table. NebulaStream is 8.5% wired (165/1945), compile-verified; Flink/Kafka unchanged at 100%.
…5 extract) Regenerate streaming-coverage.png at 224/1945 (11.5%), bump cache-bust to ?v=3, update alt text + coverage table. Flink/Kafka unchanged at 100%.
Box/span predicates wired per-event with query-literal boxes (stbox_in/tbox_in/ tstzspan_in). Regenerate streaming-coverage.png at 243/1945 (12.5%), cache-bust ?v=4.
…onfirmed Regenerate the streaming-coverage figure and table for the measured NebulaStream surface: 327 wired (16.8%), 38 confirmed callable via end-to-end systests.
…onfirmed Regenerate the streaming-coverage figure and table: 332 wired (17.1%), 43 confirmed callable via end-to-end systests (adds the single-argument temporal-transform value-output family).
…onfirmed Regenerate the streaming-coverage figure and table: 336 wired (17.3%), 47 confirmed callable (adds the geometry value-output family).
…onfirmed Regenerate the streaming-coverage figure and table: 365 wired (18.8%), 49 confirmed callable — adds the 29 cross-vehicle STBox-vs-STBox per-event predicates.
…onfirmed Regenerate the streaming-coverage figure and table: 384 wired (19.7%), 57 confirmed callable — adds the 13 tnumber-vs-tnumber cross-vehicle predicates and the merge functions invoked by the uniformized extent/union aggregates.
… cross-vehicle predicates)
… temporal combinators)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publishes profile-linked, user-facing evidence that the ecosystem is complete, correct, and ready for real-world deployment — measured, not asserted. Consolidates the scattered parity and benchmark artifacts into two uniform, peer pages linked from a new Parity & benchmarks section of the profile README.
What it adds (doc-only)
profile/streaming-parity.md— MobilityFlink / MobilityKafka / MobilityNebula. Coverage of the 1,945 streamable MEOS functions (Flink/Kafka 100% proven-callable; Nebula in progress, compile-verified), BerlinMOD query-result parity (snapshot = batch), BerlinMOD benchmark.profile/database-parity.md— MobilityDB / MobilityDuck / MobilitySpark. Coverage of the MobilityDB SQL surface (MobilityDB reference; MobilityDuck 943/943 active; MobilitySpark 1571/1577 + 29/29 dialect), cross-type parity + semantic exclusions, BerlinMOD query-result parity (#861) + cross-platform benchmark (MobilityDB-BerlinMOD #29).profile/README.md— a Parity & benchmarks section linking both.Consolidation, not duplication
Each page is a hub that summarizes and links the detailed sources — per-repo audits (
parity-status.md,parity-100.md,PARITY.md), the cross-type methodology + harness (MobilityDB #1002 / #1110 / #868), the portability contract (#861), and the benchmark report (#29). No numbers are re-derived here.Status
Present-state as of 2026-05-23. Flink/Kafka final at 100%; NebulaStream coverage, the database figures, and the benchmark tables advance as the accumulated-PR builds and dated runs land. The database-side run feeds refreshed numbers without restructuring.