Skip to content

Bulk-load table: UNIQUE or UNIQUE_HASH before against after the load, per wheel #362

Open

Description

@tae898

Problem

I want the cost of creating UNIQUE and UNIQUE_HASH indexes before versus after a bulk load, across row shapes and graph loads, on each wheel.

It is one row of the bindings study list. It was held on stale pins and re-pins after the 26.11.1 release wheels exist.

Priority: P3 (tier 3 of the re-pin order).

Acceptance

  • The study is re-pinned to the 26.11.1 pair and dry-run
  • It runs and is scored
  • The docs say when to create the index

Results and the scorer output go in this issue as comments. Numbers are generated by script from the result files, never typed.

Activity

  1. added
    pythonPull requests that update python code
    performanceSpeed or memory of the bindings, with a measurement
    on Nov 10, 2026
  2. added this to the 26.12.1 milestone on Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

performanceSpeed or memory of the bindings, with a measurementpythonPull requests that update python code

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions