| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
| Warning |
|---|
Important information: Please make sure to dimension your instance correctly from the beginning (check the minimum requirements below). The Charon-SSP license is created when the instance is first launched. Changing the number of CPU cores later will invalidate the license and thus prevent Charon instances from starting. |
General CPU requirement: Charon-SSP requires modern x86-64 architecture processors with a recommended CPU frequency of at least 3.0GHz.
The OCI non-baremetal shapes available at the time of writing offer CPU frequencies up to 2.2GHz. This limits the ability of the emulator to deliver the highest performance. Please contact Stromasys to discuss your requirements if you have any concerns.
Minimum requirements for Charon-SSP:
- 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 emulated 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.
- Charon-SSP/4U+ and Charon-SSP/4V+ must run on hardware supporting VT-x (baremetal shape). These product variants are not supported on AMD processors. Please contact Stromasys or your Stromasys VAR if you need this type of emulated SPARC hardware to discuss your requirements in detail.
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.
...