Hardware Requirements for GeognoSIS & GeognoSIS Express
All Cadcorp products are supplied in 32-bit and 64-bit versions. Cadcorp recommends that wherever possible, the appropriate architecture version matches the operating system.
Minimum
Operating system |
Windows® Server 2012 or above | |
Processor |
Intel® Xeon E-2300 series processor with up to 8 cores |
|
Memory |
16 GB |
|
Disk -Installation |
2 GB for software installation |
|
Disk -Data |
100GB (dependent on local storage) |
Recommended
Operating system | Windows® Server 2022 Standard Edition 64-bit | |
Processor |
2 x 3rd Generation Intel® Xeon® Scalable processors with up to 24 cores per processor |
|
Memory |
32 GB |
|
Disk :Installation |
2 GB for software installation |
|
Disk :Data |
100GB (dependent on local data storage) |
Additional Information
- GeognoSIS is licensed per server. Cadcorp defines a server as 32 “logical processors” on a 32-bit operating system and 64 on a 64-bit operating system. The logical processor count is often the same as the number of cores, but can differ, for example, when Hyper-Threading is enabled, or on virtual machines (which have their own resource allocation models). If GeognoSIS is installed on a server with more than the number of supported logical processors, then GeognoSIS will automatically run on the first 32 or 64 that it finds. GeognoSIS can be assigned to specific logical processors if required.
- The numbers of proposed users of the GeognoSIS service together with the types of data served will ultimately determine the specification of the server. Users of multiple GeognoSIS or GeognoSIS Express instances may wish to dedicate processors to these instances.
- The use of slave instances for WMS, WMTS and WFS service requests will require additional memory for each slave created.
- Additional local disk space may be required to store raster and other data for fast access by GeognoSIS. If you are intending to use tile caches (either pre-built or built over time from a WMTS tile service), these are best stored on the GeognoSIS server. The amount of space required will depend on the number of cached levels you are intending to use. Be aware that tile caches can take up considerable space on the server.
Using Virtual Machines
If a Virtual Server is to be used for the deployment of GeognoSIS, there are specific licensing implications and Virtual Server setup requirements that need to be addressed.
Licensing for GeognoSIS on virtual machines is locked to the processors created by the virtual machine. You should build a virtual machine to match the processors for which you are licensed to run GeognoSIS.
-
VMware allows logical processors and cores to be built, based on the host machine processor specification. A VMware server should be built to match the GeognoSIS licenses; e.g. a single GeognoSIS licence can be run on a VMware server built with up to 32 or 64 logical processors and as many cores as allowed (determined by the host machine specification).
-
Hyper-V creates logical cores without defining processors. In this case, GeognoSIS reads each logical core as a processor.