## 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 Topology & attribute fidelity 02 Local adjacency / region latency 03 Load & update cost Include memory, storage, energy and hardware writes # Meshes | 8DB Product reference. Reviewed 18 September 2026. Implementation and evaluation scope are stated below. Explore the models (https://8braid.com/modalities) / 8DB Meshes Keep the surface, and what it describes. Represent connected geometry for applications that need more than disconnected spatial samples. Explore the capabilities See a complete workload Connect · surface · inspect Model / Meshes Conceptual diagram [Diagram: meshes representation: conceptual diagram] Vertices and faces form a surface. A selected face remains connected to its neighbors. Capabilities What changes Input to value Alternatives Performance Adoption Related articles Reference Start with the operations your question needs. Typed triangular mesh values Spatial vertices with triangle connectivity Related geometry records and source relationships Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application. A mesh type is not a complete CAD, rendering or simulation package. Verify each required geometry operation and format importer. This page does not assert automatic remeshing or physical simulation. Connected native models Keep the next question within reach. Typed connectivity retains a distinction that an unstructured bag of coordinates would lose. Keeping that representation beside source records opens a path from a selected surface region to its measurement context. [Diagram: point clouds representation: conceptual diagram] Point clouds Find structure in a field of points. Sample · search · inspect Explore model ↗ (https://8braid.com/modalities/point-clouds) [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 Review a component surface and the evidence behind it 0 1 Import geometry → 0 2 Keep connectivity → 0 3 Select a region → 0 4 Connect observations → 0 5 Review the surface → [Diagram: meshes representation: conceptual diagram] Step 1 / Meshes Import supported geometry and source metadata Vertices and faces form a surface. A selected face remains connected to its neighbors. Next: Keep connectivity 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 Import supported geometry and source metadata Preserve vertices and triangle connectivity Select a surface region in the application Resolve associated point observations and inspection records Present a reviewable surface with its measurement context The full job may include a renderer or geometry library. Show these dependencies explicitly; native storage does not remove every specialist tool. Compare a realistic alternative. Geometry functions and specialist mesh tools remain relevant alternatives. Compare the exact operators and fidelity, then the effort to keep the surface linked to application evidence. 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. Topology/attribute round-trip fidelity; import/export time; selected-region retrieval; resident memory; mesh plus index size; full review-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 8DB | What Can Geometry Reveal That Data Points Alone Cannot? (https://8braid.com/journal/one-mathematical-object-six-views-what-a-table-of-samples-can-never-ask) 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/meshes.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)