Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-282

EXASolo does not use more RAM after increase in VM RAM

    Details

    • Symptoms:
      Hide

      No performance improvement in EXASolo even although more RAM has been allocated to the virtual machine.

      Show
      No performance improvement in EXASolo even although more RAM has been allocated to the virtual machine.
    • Explanation:
      Hide

      EXASolo evaluates the VMs available resources only during its first start. If the VMs RAM is subsequently increased via VM configuration (e.g. VirtualBox), the DB will not update this parameter automatically.

      Show
      EXASolo evaluates the VMs available resources only during its first start. If the VMs RAM is subsequently increased via VM configuration (e.g. VirtualBox), the DB will not update this parameter automatically.
    • Solution:
      Hide

      Therefore, if you want to allocate more RAM to the DB, you have to setup this parameter in EXAOperation after you have changed the VM:

      1. Open EXAOperation: As it is web-based, it can be reached via HTTP/HTTPS ports with a browser. Usually you can use the IP address shown on the EXASolo configuration window
      2. Log in: Standard user / password are admin / admin.
      3. Check DB RAM: On page “EXASolution” (usually the page that opens at default) it shows the DB instance running with a few parameters. Look at “DB RAM”. This should be ~90% of the VM RAM.
      4. *Shut down the database
      5. Change DB RAM: If you want to change this parameter, click on the DB instance name, then click the “Edit” button on the lower left. On the following page you can change the parameter “* DB RAM (GiB)” (it’s the second to last one below).
      6. *Start the database

      Caution!

      If you setup some RAM size that is too close to VMs RAM it will not leave sufficient RAM for the OS, forcing that to swap. So if performance deteriorates significantly make sure to leave enough RAM free (check OS swap in profiling tables). It is recommended to have at least 10% of the VM reserved for the OS.

      Show
      Therefore, if you want to allocate more RAM to the DB, you have to setup this parameter in EXAOperation after you have changed the VM: Open EXAOperation: As it is web-based, it can be reached via HTTP/HTTPS ports with a browser. Usually you can use the IP address shown on the EXASolo configuration window Log in: Standard user / password are admin / admin. Check DB RAM: On page “EXASolution” (usually the page that opens at default) it shows the DB instance running with a few parameters. Look at “DB RAM”. This should be ~90% of the VM RAM. *Shut down the database Change DB RAM: If you want to change this parameter, click on the DB instance name, then click the “Edit” button on the lower left. On the following page you can change the parameter “* DB RAM (GiB)” (it’s the second to last one below). *Start the database Caution! If you setup some RAM size that is too close to VMs RAM it will not leave sufficient RAM for the OS, forcing that to swap. So if performance deteriorates significantly make sure to leave enough RAM free (check OS swap in profiling tables). It is recommended to have at least 10% of the VM reserved for the OS.
    • Category 1:
      Cluster Administration
    • Category 2:
      Database Administration

      Attachments

        Activity

          People

          • Assignee:
            CaptainEXA Captain EXASOL
            Reporter:
            CaptainEXA Captain EXASOL
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: