Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: small correction

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

  • Minimum number of host system CPU cores:
    • At least one CPU core for the host operating system.
    • For each emulated SPARC system:
      • One CPU core for each emulated CPU of the instance.
      • At least one additional CPU core for I/O. If server JIT optimization is used, add an additional I/O CPU for improved translation speed.
  • Minimum memory requirements:
    • At least 2GB of RAM for the host operating system.
    • For each emulated SPARC system:
      • The configured memory of the instance.
      • 2GB of RAM (6GB of RAM if server JIT is used) to allow for DIT optimization, emulator requirements, run-time buffers, SMP and graphics emulation.
  • One or more network interfaces, depending on customer requirements. The network performance level of an instance type provides an indication of the data transfer rates to be expected from the AWS instance.
  • Charon-SSP/4U+ and Charon-SSP/4V+ must run on hardware supporting VT-x. For this, you need to select an instance with the suffix metal in the name. If you consider running Charon-SSP/4U+ or 4V+ in AWS to achieve better performance, please contact Stromasys or a Stromasys VAR for additional information.

(warning) Please note that the sizing guidelines above—in particular regarding number of host CPU cores and host memory—show the minimum requirements. Every use case has to be reviewed and the actual host sizing has to be adapted as necessary. For example, the number of I/O CPUs may have to be increased if the guest applications produce a high I/O load. Also take into consideration that a system with many emulated CPUs in general is also able to create a higher I/O load and thus the number of I/O CPUs may have to be raised. 

...

(warning) It is recommended to create separate storage space (using AWS EBS volumes) for Charon application data (e.g., disk images). If required, such volumes can later easily be migrated to another instance (see Storage Management).

...