Hi George,
32 GB RAM is more than enough but you need to make sure it is being used by Spectrum.
- I would set the Remote Components to match the number of CPU on the server. (which you have).
- Increase the max memory to 8192MB (assuming there is currently at least 8GB unused when Spectrum is running, leave some for the OS too).
Have a look at your Java Properties too, the ones that relate to the pool size are the most important for performance, I would recommend sticking to the values listed on this site unless you have a good reason to change them (pool.file for TAB data, pool.database for SQL data).
Another thing to consider is the amount and complexity of your data:
- Deaggregate complex aggregate geometries (they stop spatial Indexes from working efficiently).
- Simplify overly complex data by removing unnecessary nodes (thinning).
- Limit the number of complex layers that are visible, you can do this by turning them off by default or using zoom layering.
- For very heavy layers that are static (contours, vegetation, flooding, etc) you can setup a NamedTile and enable tile caching.
- Make sure SQL tables have appropriate spatial indexes.
I would be interested to see if Precisely or anyone else has any other suggestions.
------------------------------
Duri Bradshaw
Spatial IT Consultant
Insight GIS
------------------------------
Original Message:
Sent: 11-01-2023 21:33
From: George Corea
Subject: Common server config/resources for public SSA instances
We have found that some public SSA sites are slugish and was wondering what resources you have available that make them better.
Typically the system is on Spectrum/SSA 2023 and
Spectrum settings
Are there any non-default settings you use?
What network up/down speeds are yours typically on?
Regards,
------------------------------
George Corea
Data Guru
Mangoesmapping
MOOMIN QLD
------------------------------