Bisq Wiki - User contributions [en]

Reducing memory usage

2020-04-15T15:26:24Z

Ghubstan: /* Default MaxRAM Setting */

== Default MaxRAM Setting ==

One of the settings java virtual machines (JVMs) use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM's default MaxRAM configuration is too large.    To check the default MaxRAM setting, run this java <code>version</code> command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the MaxRAM value (bytes) in the output; this machine says

367: uint64_t MaxRAM = 137438953472

This means the OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments have shown running Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% (when starting a clean Bisq installation with an empty data directory).
   Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.

As of version 1.3.2, Bisq is started with a MaxRAM setting of 4g (GB).    If you are using Bisq v1.3.1 or older, consider upgrading to the [https://bisq.network/downloads latest version] to benefit from this change.

Reducing memory usage

2020-04-12T13:00:33Z

Ghubstan:

== Default MaxRAM Setting ==

One of the settings java virtual machines (JVMs) use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM's default MaxRAM configuration is too large.    To check the default MaxRAM setting, run this java <code>version</code> command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the MaxRAM value (bytes) in the output; this machine says

367: uint64_t MaxRAM = 137438953472

This means the OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments have shown running Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% (when starting a clean Bisq installation with an empty data directory).
   Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.

As of version 1.3.[TODO], Bisq is started with a MaxRAM setting of 4g (GB).    If you are using Bisq v1.3.[TODO] or older, consider upgrading to the [https://bisq.network/downloads latest version] to benefit from this change.

Reducing memory usage

2020-04-08T13:23:33Z

Ghubstan:

== Default MaxRAM Setting ==

One of the settings java virtual machines use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM's default MaxRAM configuration is too large.    To check the default MaxRAM setting, run this java 'version' command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the MaxRAM value (bytes) in the output; this machine says

367: uint64_t MaxRAM = 137438953472

meaning my OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments have shown running Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% (when starting a clean Bisq installation with an empty data directory).
   Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.

As of version 1.2.7, Bisq is started with a MaxRAM setting of 4g (GB).    If you are using Bisq v1.2 [.TODO] or older, consider upgrading to the [https://bisq.network/downloads latest version] to benefit from this change.

Linux memory arenas

2020-04-05T20:28:21Z

Ghubstan:

== Java Threads and Linux Memory Arenas ==

With the intention of improving efficiency of memory access in multi-threaded applications, [https://www.gnu.org/software/libc/manual/html_mono/libc.html glibc] may create more memory regions (known as [https://sourceware.org/glibc/wiki/MallocInternals#Arenas_and_Heaps arenas]) than necessary.    In some cases, multi-threaded java applications allocating few and small objects can trigger creation of one arena for each of those threads, resulting in large growth of the java process' resident memory, no matter how well on-heap memory is managed by the application.

One way to limit arena creation in Bisq is to define the environment variable MALLOC_ARENA_MAX=4.

export MALLOC_ARENA_MAX=4

If not set (default=0), a combination of applications may create as many arenas as the number of cpu cores * 8.

This setting reduced resident memory use by ~300 MB, and reduced virtual memory use by ~3.7 GB on an 8 core, 16 GB RAM machine running Ubuntu 18. The trade off for reducing resident memory use in this manner is the added cost of the contention between threads for memory access among fewer arenas, but this was not perceptible during testing and profiling.   (The major bottlenecks in Bisq performance are related to Tor/P2P network I/O.)

There are many sources of information on this and other tunable memory allocation parameters, starting with the Linux [http://man7.org/linux/man-pages/man3/mallopt.3.html mallopt] man page; additional research and troubleshooting tips are welcome.

Reducing memory usage

2020-04-05T19:45:11Z

Ghubstan:

== Default MaxRAM Setting ==

One of the settings java virtual machines use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM's default MaxRAM configuration is too large.    To check the default MaxRAM setting, run this java 'version' command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the MaxRAM value (bytes) in the output; this machine says

367: uint64_t MaxRAM = 137438953472

meaning my OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments have shown running Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% (when starting a clean Bisq installation with an empty data directory).
   Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.

As of version 1.2.7, Bisq is started with a MaxRAM setting of 4g (GB).    If you are using Bisq v1.2.6 or older, consider upgrading to the [https://bisq.network/downloads latest version] to benefit from this change.

Reducing memory usage

2020-04-05T19:44:30Z

Ghubstan: /* Default MaxRAM Setting */

== Default MaxRAM Setting ==

One of the settings java virtual machines use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM's default MaxRAM configuration is too large.    To check the default MaxRAM setting, run this java 'version' command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the default MaxRAM setting in the output; this machine says

367: uint64_t MaxRAM = 137438953472

meaning my OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments have shown running Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% (when starting a clean Bisq installation with an empty data directory).
   Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.

As of version 1.2.7, Bisq is started with a MaxRAM setting of 4g (GB).    If you are using Bisq v1.2.6 or older, consider upgrading to the [https://bisq.network/downloads latest version] to benefit from this change.

Reducing memory usage

2020-04-05T19:43:46Z

Ghubstan:

== Default MaxRAM Setting ==

One of the settings java virtual machines use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM's MaxRAM setting is too large.    To check the default MaxRAM setting, run this java 'version' command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the default MaxRAM setting in the output; this machine says

367: uint64_t MaxRAM = 137438953472

meaning my OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments have shown running Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% (when starting a clean Bisq installation with an empty data directory).
   Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.

As of version 1.2.7, Bisq is started with a MaxRAM setting of 4g (GB).    If you are using Bisq v1.2.6 or older, consider upgrading to the [https://bisq.network/downloads latest version] to benefit from this change.

Linux memory arenas

2020-04-05T19:41:46Z

Ghubstan:

== Java Threads and Linux Memory Arenas ==

With the intention of improving efficiency of memory access in multi-threaded applications, [https://www.gnu.org/software/libc/manual/html_mono/libc.html glibc] may create more memory regions (known as [https://sourceware.org/glibc/wiki/MallocInternals#Arenas_and_Heaps arenas]) than necessary.    In some cases, multi-threaded java applications allocating few and small objects can trigger creation of one arena for each of those threads, resulting in large growth of the java process' resident memory, no matter how well on-heap memory is managed by the application.

One way to limit arena creation in Bisq is to define the environment variable MALLOC_ARENA_MAX=4.

export MALLOC_ARENA_MAX=4

If not set (default=0), a combination of applications may create as many arenas as the number of cpu cores * 8.

This setting reduced resident memory use by ~300 MB, and reduced virtual memory use by ~3.7 GB on an 8 core, 16 GB RAM machine running Ubuntu 18. The trade off for reducing resident memory use in this manner is the added cost of the contention among threads for memory access among fewer arenas, but this was not perceptible during testing and profiling.   (The major bottlenecks in Bisq performance are related to Tor/P2P network I/O.)

There are many sources of information on this and other tunable memory allocation parameters, starting with the Linux [http://man7.org/linux/man-pages/man3/mallopt.3.html mallopt] man page; additional research and troubleshooting tips are welcome.

Troubleshooting

2020-04-05T15:35:13Z

Ghubstan: /* Bisq is using too much RAM */

This article is a stub. The specific sections below are just examples for demonstration purposes.

__TOC__

== Bisq won't start ==

== My Antivirus software flags Bisq as malware ==

== Bisq cannot connect via Tor ==

== My wallet has an incorrect balance ==

* Resyncing your simplified payment verification (SPV) file may resolve this. See [[Delete and resync SPV file]]

== Bisq is using too much RAM ==

* Limiting the maximum amount of RAM the JVM is allowed to use may resolve this. See [[Reduce JVM MAXRam]]

* On Linux, restricting memory arena allocation can reduce Bisq's off-heap memory consumption. See [[Linux_Memory_Arenas]]

== My problem isn't addressed here ==

See [[user support]]

[[Category:Stubs]]
[[Category:Client]]

Reducing memory usage

2020-04-05T15:26:27Z

Ghubstan: /* Default MaxRAM Setting */

== Default MaxRAM Setting ==

One of the settings java virtual machines use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM thinks it has more RAM to use than is installed on your machine.    To check the default MaxRAM setting, run this java 'version' command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the default MaxRAM setting in the output; this machine says

367: uint64_t MaxRAM = 137438953472

meaning my OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments have shown running Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% (when starting a clean Bisq installation with an empty data directory).
   Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.

As of version 1.2.7, Bisq is started with a MaxRAM setting of 4g (GB).    If you are using Bisq v1.2.6 or older, consider upgrading to the [https://bisq.network/downloads latest version] to benefit from this change.

Reducing memory usage

2020-04-05T15:21:48Z

Ghubstan: /* Default MaxRAM Setting */

== Default MaxRAM Setting ==

One of the settings java virtual machines use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM thinks it has more RAM to use than is installed on your machine. To check the default MaxRAM setting, run this java 'version' command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the default MaxRAM setting in the output; this machine says

367: uint64_t MaxRAM = 137438953472 {pd product} {default}

meaning my OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments have shown running Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% (when starting a clean Bisq installation with an empty data directory).

Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.

As of version 1.2.7, Bisq starts up with a MaxRAM setting of 4g (GB). If you are using Bisq v1.2.6 or older, consider upgrading to the [https://bisq.network/downloads latest version] to reduce Bisq's RAM usage.

Linux memory arenas

2020-04-05T15:19:08Z

Ghubstan:

== Java Threads and Linux Memory Arenas ==

With the intention of improving efficiency of memory access in multi-threaded applications, [https://www.gnu.org/software/libc/manual/html_mono/libc.html glibc] may create more memory regions (known as [https://sourceware.org/glibc/wiki/MallocInternals#Arenas_and_Heaps arenas]) than necessary.    In some cases, multi-threaded java applications allocating few and small objects in some threads can trigger creation of one arena for each of those threads, resulting in large growth of the java process' resident memory, no matter how well on-heap memory is managed by the application.

One way to limit arena creation in Bisq is to define the environment variable MALLOC_ARENA_MAX=4.

export MALLOC_ARENA_MAX=4

If not set (default=0), a combination of applications may create as many arenas as the number of cpu cores * 8.

This setting reduced resident memory use by ~300 MB, and reduced virtual memory use by ~3.7 GB on an 8 core, 16 GB RAM machine running Ubuntu 18. The trade off for reducing resident memory use in this manner is the added cost of the contention among threads for memory access among fewer arenas, but this was not perceptible during testing and profiling.   (The major bottlenecks in Bisq performance are related to Tor/P2P network I/O.)

There are many sources of information on this and other tunable memory allocation parameters, starting with the Linux [http://man7.org/linux/man-pages/man3/mallopt.3.html mallopt] man page; additional research and troubleshooting tips are welcome.

Reducing memory usage

2020-04-05T12:52:48Z

Ghubstan:

== Default MaxRAM Setting ==

One of the settings java virtual machines use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM thinks it has more RAM to use than is installed on your machine. To check the default MaxRAM setting, run this java 'version' command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the default MaxRAM setting in the output; this machine says

367: uint64_t MaxRAM = 137438953472 {pd product} {default}

meaning my OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments have shown starting Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% when starting a clean Bisq installation -- with an empty data directory.

Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.

As of version 1.2.7, Bisq starts up with a MaxRAM setting of 4g (GB). If you are using Bisq v1.2.6 or older, consider upgrading to the [https://bisq.network/downloads latest version] to reduce Bisq's RAM usage.

Troubleshooting

2020-04-04T17:39:55Z

Ghubstan: /* Bisq is using too much RAM */

This article is a stub. The specific sections below are just examples for demonstration purposes.

__TOC__

== Bisq won't start ==

== My Antivirus software flags Bisq as malware ==

== Bisq cannot connect via Tor ==

== My wallet has an incorrect balance ==

* Resyncing your simplified payment verification (SPV) file may resolve this. See [[Delete and resync SPV file]]

== Bisq is using too much RAM ==

* Limiting the maximum amount of RAM the JVM thinks your machine has may resolve this. See [[Reduce JVM MAXRam]]

* On Linux, restricting memory arena allocation can reduce Bisq's off-heap memory consumption. See [[Linux_Memory_Arenas]]

== My problem isn't addressed here ==

See [[user support]]

[[Category:Stubs]]
[[Category:Client]]

Reducing memory usage

2020-04-04T17:15:55Z

Ghubstan:

== Default MaxRAM Setting ==

One of the settings java virtual machines use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM thinks it has more RAM to use than is installed on your machine. To check the default MaxRAM setting, run this java 'version' command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the default MaxRAM setting in the output; this machine says

367: uint64_t MaxRAM = 137438953472 {pd product} {default}

meaning my OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments have shown starting Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% when starting a clean Bisq installation -- with an empty data directory.

Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.

As of version 1.2.7, Bisq starts up with a MaxRAM setting of 4g (GB). If you are using Bisq v1.2.6 or older, consider upgrading to the latest version to reduce Bisq's RAM usage.

Troubleshooting

2020-04-04T17:06:01Z

Ghubstan:

This article is a stub. The specific sections below are just examples for demonstration purposes.

__TOC__

== Bisq won't start ==

== My Antivirus software flags Bisq as malware ==

== Bisq cannot connect via Tor ==

== My wallet has an incorrect balance ==

* Resyncing your simplified payment verification (SPV) file may resolve this. See [[Delete and resync SPV file]]

== Bisq is using too much RAM ==

* Limiting the maximum amount of RAM the JVM thinks your machine has may resolve this. See [[Reduce JVM MAXRam]], and [[Linux_Memory_Arenas]]

== My problem isn't addressed here ==

See [[user support]]

[[Category:Stubs]]
[[Category:Client]]

Linux memory arenas

2020-04-04T17:05:18Z

Ghubstan: Created page with "TODO"

TODO

Reducing memory usage

2020-04-04T17:03:06Z

Ghubstan: Created page with "== Default MaxRAM Setting == One of the settings java virtual machines use to calibrate how much physical memory to reserve at startup is called MaxRAM, and there is a good c..."

== Default MaxRAM Setting ==

One of the settings java virtual machines use to calibrate how much physical memory to reserve at startup is called MaxRAM, and there is a good chance your JVM thinks it has more RAM to use than is installed on your machine. To check the default MaxRAM setting, run this java 'version' command:

java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM

Look for the default MaxRAM setting in the output; this machine says

367: uint64_t MaxRAM = 137438953472 {pd product} {default}

meaning my OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.

Experiments has shown that starting Bisq with a 4GB MaxRAM setting more than halves the resident memory consumption when starting a clean Bisq installation (with an empty data directory). Setting MaxRAM = 2GB reduces resident memory usage even more, but setting it any lower (1.5GB) will result in an OutOfMemoryError and crash the app.

As of version 1.2.7, Bisq starts up with a MaxRAM setting of 4GB.

Troubleshooting

2020-04-04T16:39:31Z

Ghubstan:

This article is a stub. The specific sections below are just examples for demonstration purposes.

__TOC__

== Bisq won't start ==

== My Antivirus software flags Bisq as malware ==

== Bisq cannot connect via Tor ==

== My wallet has an incorrect balance ==

* Resyncing your simplified payment verification (SPV) file may resolve this. See [[Delete and resync SPV file]]

== Bisq is using too much RAM ==

* Limiting the maximum amount of RAM the JVM thinks your machine has may resolve this. See [[Reduce JVM MAXRam]]

== My problem isn't addressed here ==

See [[user support]]

[[Category:Stubs]]
[[Category:Client]]