Skip to content

Conversation

@ghalliday
Copy link
Member

@ghalliday ghalliday commented Nov 28, 2025

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

@github-actions
Copy link

Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-35430

Jirabot Action Result:
Assigning user: [email protected]
Workflow Transition To: Merge Pending
Updated PR

Copilot finished reviewing on behalf of ghalliday November 28, 2025 14:39
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR increases the maximum compression ratio for HPCC index tree leaf nodes from 25x to 50x, allowing more aggressive compression of highly compressible data while still limiting memory usage when the compressed data is read.

  • Changed maxCompressionFactor from 25 to 50 in the InplaceKeyBuildContext structure
  • Updated the corresponding comment to reflect the new ratio (2% instead of 4%)

struct {
double minCompressionThreshold = 0.95; // use uncompressed if compressed is > 95% uncompressed
unsigned maxCompressionFactor = 25; // Don't compress payload to less than 4% of the original by default (beause when it is read it will use lots of memory)
unsigned maxCompressionFactor = 50; // Don't compress payload to less than 2% of the original by default (beause when it is read it will use lots of memory)
Copy link

Copilot AI Nov 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spelling error: "beause" should be "because".

Suggested change
unsigned maxCompressionFactor = 50; // Don't compress payload to less than 2% of the original by default (beause when it is read it will use lots of memory)
unsigned maxCompressionFactor = 50; // Don't compress payload to less than 2% of the original by default (because when it is read it will use lots of memory)

Copilot uses AI. Check for mistakes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, sure

Copy link
Contributor

@mckellyln mckellyln left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.
But because is spelled incorrectly.

@ghalliday ghalliday merged commit aa7c65d into hpcc-systems:candidate-9.14.x Dec 2, 2025
21 checks passed
@github-actions
Copy link

github-actions bot commented Dec 2, 2025

Jirabot Action Result:
Fix versions already added.
Workflow Transition: 'Resolve issue'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants