Skip to content

bindings-ab: port the ingest, UDF and callback arms to the release wheels and run the A/B #353

Open

Description

@tae898

Problem

The long bindings A/B study still measures an old humemai cp312 wheel. The result applies to old code, so it cannot support a claim about the shipped arcadedb and arcadedb-jvm wheels.

I want one A/A pair per tier family and package in the plan, so every verdict carries its own noise floor, and the study runs last in the timed queue.

Priority: P4.

Acceptance

  • Only the ingest (dataframe, Arrow, columns), UDF and callback arms are ported to the arcadedb and arcadedb-jvm 26.11.1 wheels (import name arcadedb), the materialize arm is dropped
  • The A/A pairs are in the plan and the checksums are refreshed
  • A dry run at small N passes and the estimate is refreshed
  • The study runs and its verdict is recorded

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

jvmThe arcadedb-jvm package (JPype build)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