## Performance evidence update / 18 September 2026 MODALITY PERFORMANCE / EVIDENCE REVIEWED 18 SEPTEMBER 2026 Define the useful result. Measure the complete job. A modality-specific timing is not yet linked to this guide. There may be supporting engineering measurements in the internal archive. We are reconciling their workload, result quality and comparison conditions before presenting a public chart. A benchmark for an adjacent model does not establish this model’s performance. 01 Point density & answer quality 02 Neighborhood query latency 03 Load & index memory Include memory, storage, energy and hardware writes # Point clouds | 8DB Product reference. Reviewed 18 September 2026. Implementation and evaluation scope are stated below. Explore the models (https://8braid.com/modalities) / 8DB Point clouds Find structure in a field of points. Work with sampled geometry and supported attributes, then connect spatial neighborhoods to the broader observation. Explore the capabilities See a complete workload Sample · search · inspect Model / Point clouds Conceptual diagram [Diagram: point clouds representation: conceptual diagram] A point sample outlines a surface. Highlighted neighbors identify a local region of interest. Capabilities What changes Input to value Alternatives Performance Adoption Related articles Reference Start with the operations your question needs. XYZ nearest-neighbour queries Region queries and confidence-aware filtering Rejection of nonfinite coordinates on recorded execution paths Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application. Attribute coverage and retention depend on the representation. A downsampled view need not retain every source attribute. Registration, segmentation and defect classification are separate operations to qualify. Connected native models Keep the next question within reach. A point set is more useful when the application can follow it back to the observation and forward to the asset’s inspection history. 8DB’s native shapes and relationships provide building blocks for that workflow. [Diagram: meshes representation: conceptual diagram] Meshes Keep the surface, and what it describes. Connect · surface · inspect Explore model ↗ (https://8braid.com/modalities/meshes) [Diagram: graphs representation: conceptual diagram] Graphs Follow the relationship to a better answer. Connect · traverse · follow Explore model ↗ (https://8braid.com/modalities/graphs) [Diagram: documents representation: conceptual diagram] Documents Keep the source behind the answer. Structure · search · trace Explore model ↗ (https://8braid.com/modalities/documents) These connections show the models involved in the application design. Compare the supported combination and full workflow with a realistic alternative. Input → usable value / interactive design example Inspect the measured surface around a component 0 1 Receive a scan → 0 2 Validate coordinates → 0 3 Select neighbors → 0 4 Connect inspections → 0 5 Review the evidence → [Diagram: point clouds representation: conceptual diagram] Step 1 / Point clouds Receive an XYZ scan with capture metadata A point sample outlines a surface. Highlighted neighbors identify a local region of interest. Next: Validate coordinates Conceptual application workflow. Qualify the supported operations, external tools, protection and persistence for the complete path. These diagrams are explanatory, not measured results. Read the complete workflow and comparison scope Receive an XYZ scan with capture metadata Validate coordinates and retain the source link Select a component region and nearby points Relate the selected points to geometry and earlier inspections Present the measured evidence for an inspection decision Count decoding, registration if required, storage/indexing and evidence assembly. A neighbourhood-query benchmark alone is not a defect-detection result. Compare a realistic alternative. Spatial stacks are realistic alternatives. Use their supported dimensionality and functions as the baseline; include any separate scan-processing library actually required by the job. PostGIS reference (https://8braid.com/modalities/https://postgis.net/docs/manual-3.6/reference) Compare equivalent outputs and required guarantees, including the simplest single-product alternative where one exists. A specialist may remain the better fit when its operators, ecosystem or operational maturity are decisive. Combining native models becomes valuable when your actual question crosses them. Performance & resources Measure the work that delivers the answer. Neighbour/region correctness; coordinate and attribute fidelity; index/build time; query latency by point count; bytes and full inspection-view latency. This draft does not assign a new speed ratio or score to this modality. Existing measurements and source leads are retained in the evidence programme; a qualified public result must identify the particular operation and path tested. Explore the published benchmark evidence (https://8braid.com/benchmarks) What belongs inside the timer and resource budget? For input-to-value testing, declare the input state and the consumer-ready output first. Include parsing, derivation, storage/protection, index readiness, querying, result assembly and delivery as applicable. Identify amortized setup and any work deferred past the finish line. Report database-stage and full-job results separately. Do not add unrelated medians or p95 values, or multiply component speedups into a claimed workflow result. Energy needs measured joules; reduced handoffs alone do not establish a saving. Choose the path that fits your deployment. Verify the supported API/SDK, data format, persistence and indexing behaviour for the release you plan to use. Match the operation-by-modality protection profile and device qualification to the workload. Post-quantum protection (https://8braid.com/pqc) · Plan a workload evaluation (https://8braid.com/build) Related articles Take the next step into the thinking. Mechanism & application 8DB | Native Multimodal Data: Connect the Dots Across Graphs, Maps and Time Series (https://8braid.com/journal/modality-is-a-projection) Explore the ideas and implementation context behind this capability. Mechanism & application Show Your Work: Provenance as a Query, Not a Forensic Reconstruction (https://8braid.com/journal/show-your-work-provenance-as-a-query) Explore the ideas and implementation context behind this capability. Reference / Reviewed 17 September 2026 Readable, shareable and traceable. This reference explains 8DB’s public modality description (https://8braid.com/modalities#explore) with an explicit workload and selection criteria. It is a documentary review, not fresh execution of every operator or platform. Public sources: 8DB modality scope (https://8braid.com/modalities) ; PostGIS reference (https://8braid.com/modalities/https://postgis.net/docs/manual-3.6/reference) ; the related articles above. Internal source leads and outstanding release checks remain in the editorial record. Download this reference (https://8braid.com/modality-reference/point-clouds.md) Evaluate the question your application needs to answer. Bring the data shapes, input state, expected output and the systems you use today. Define a comparison around that complete job. Discuss your workload (https://8braid.com/build)