Repository navigation
feat(engine): the largest project follows the computer's memory (#1615) #1639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
pick2510
merged 5 commits into
opengeos:main
from
pick2510:fix/project-limit-follows-memory
Nov 8, 2026
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
6697bfd
feat(engine): the largest project follows the computer's memory (#1615)
pick2510 845c024
fix(engine): plan the project limit for attribute-heavy data and neve…
pick2510 ddb3900
fix(engine): a 16 GB computer opens #1615's project; a 32-bit build's…
pick2510 be1a8b6
fix(engine): a 32-bit build keeps the 512 MiB project limit
pick2510 4969545
fix(engine): a refused project names the memory that opens it
pick2510 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Design question (medium-low confidence): the planning ratio now sits below the densest measured case. The doc comment measures 5.2 bytes of memory per byte of file for 30 one-letter attributes, and this constant is 5. The earlier thread's answer planned 6, "above the most measured". The change to 5 is new since that answer, and it removes the margin. At the limit, the densest measured data takes about 26% of memory rather than a quarter, and a denser hostile file takes more. The doc line "about as much as a byte of file can cost" is also not established by one measured shape. Either keep 6 (which still opens #1615's 659 MiB file on 16 GB) or soften the comment to say the ratio was measured on the shapes listed and is not a bound.