ChristophA
IS-IT--Management
When calling Mercator 6.7 Command Engine on HP-UX (from the shell) I detect a varying latency of 2-20 seconds before this instance processes a specified map or asks for a map.
If I concatenate several maps to be processed by one Mercator instance Mercator takes this "warm up time" only for the first map. Subsequent maps are processed without latency.
The behaviour is map independant and even is shown if a plain command "mercator" is issued.
There should be enough memory and disk space on the machine.
Mercator 6.7 is an installation to migrate to. But I need a solution to this idle time issue before setting this version into production.
Do you have similar experience or solution hints?
If I concatenate several maps to be processed by one Mercator instance Mercator takes this "warm up time" only for the first map. Subsequent maps are processed without latency.
The behaviour is map independant and even is shown if a plain command "mercator" is issued.
There should be enough memory and disk space on the machine.
Mercator 6.7 is an installation to migrate to. But I need a solution to this idle time issue before setting this version into production.
Do you have similar experience or solution hints?