Add additional valid starting VM arguments #954
Conversation
This file contains 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
These were introduced in Java 8u191 (2018-10-16). An important note on `MinRAMPercentage`: it is only used on ''small'' heap sizes (think <100M). It is primarily used for container applications. The properties match the following requirements: * No `"` or `%` character (the double values do not include `%`) * Values include `.` (0x2E) and 0-9 (0x30-0x39); that is between `0x20` and `0x17E` * The strings do not include `\` While these properties were originally introduced for containers, they are also useful for desktop applications. Of specific note, `MaxRAMPercentage` is useful for applications that can have a _small_ amount of data in memory to a _large_ amount of data in memory. Default values: * InitialRAMPercentage: 1.5625 * MinRamPercentage: 50.0 * MaxRamPercentage: 25.0
josmmirror
pushed a commit
to JOSM/josm
that referenced
this pull request
Sep 9, 2024
This does not currently work for WebStart, see AdoptOpenJDK/IcedTea-Web#954 . As noted in the ticket, all supported MS Windows and Apple macOS machines have 4G+ of RAM. Linux machines don't have a baseline, and some have 1G or less. Where we detect that a machine has <8G of memory in the linux start scripts, we don't add the JVM parameters. As a reminder to everyone reading the changelog: just because we ''ask'' for the ability to use 75% of the system memory doesn't mean we will ''use'' all of that memory. The JVM ''will'' free up unused memory for the rest of the system. We additionally set the minimum memory allocation to 256m; while this ''can'' be lower, that is for minimal amounts of data loaded. A clean JOSM install will use 99mb, for example. But once we add a minimal amount of data and a background layer, static memory usage goes up to 161mb. git-svn-id: https://josm.openstreetmap.de/svn/trunk@19215 0c6e7542-c601-0410-84e7-c038aed88b3b
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These were introduced in Java 8u191 (2018-10-16).
An important note on
MinRAMPercentage: it is only used on ''small'' heap sizes (think <100M). It is primarily used for container applications.The properties match the following requirements:
"or%character (the double values do not include%).(0x2E) and 0-9 (0x30-0x39); that is between0x20and0x17E\While these properties were originally introduced for containers, they are also useful for desktop applications. Of specific note,
MaxRAMPercentageis useful for applications that can have a small amount of data in memory to a large amount of data in memory.Default values: