GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Write regression after release 0.8.3 · Issue #268 · lmdbjava/lmdbjava

Write regression after release 0.8.3 #268

New issue
Copy link
New issue
Copy link
Closed
Closed
Write regression after release 0.8.3#268
Copy link

Description

@bp-alex
bp-alex
opened on Nov 3, 2025
Issue body actions

Following #262, I executed the version regression benchmark suite. The current results show significant write performance regression after release 0.8.3.

I subsequently developed an automated bisection capability in the LmdbJava Benchmarks project. This identified the regression:


  Commit   Date                    Score    Change     Message
========================================================================================================================
   be2a15b  2023-02-04 00:28:16     89.07             [maven-release-plugin] prepare release lmdbjava-0.8.3
   1cc7e6c  2023-12-04 07:42:08     94.49     +6.09%  Test on Java 21
   f17b63f  2023-12-05 01:34:17     91.57     -3.09%  [maven-release-plugin] prepare release lmdbjava-0.9.0
   b5dfb25  2025-02-16 23:37:16     91.38     -0.21%  Uplift lmdb from 0.9.29 to 0.9.31 (#245)
 * 68f0a44  2025-02-16 23:46:30    128.63    +40.76%  Add DbiFlags#MDB_UNSIGNEDKEY to allow to compare byte array, Byt...
   928cf7b  2025-02-20 01:26:13    129.12     +0.38%  Add url element to pom.xml to satisfy OSSRH deployment rules
   dc24f4b  2025-10-31 00:20:59    122.03     -5.49%  Generalise benchmark link

The regression emerged in commit 68f0a44, which modifies comparator logic. This represents a 40.76% write performance degradation from the previous commit.

Given @at055612 is undertaking significant comparator changes in #249 and #250, this regression is likely to be addressed in that work. The bisection tooling is now available to verify performance impact of changes.

Activity

  1. bp-alex
    closed this as completedin ab6a6a0on Nov 4, 2025
  2. at055612
    added a commit that references this issue on Nov 4, 2025

    Resolve write performance regression (fixes lmdbjava#268)

    This issue will close once commit ab6a6a0 is merged into the 'master' branch.
    ab6a6a0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.