Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mercator 6.7, HP-UX: waiting time when starting command server

Status
Not open for further replies.

ChristophA

IS-IT--Management
Mar 25, 2002
3
DE
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?

 
Turn on audit log to see start time, change your shell script to touch a file to see time stamp before calling the executable. Do you call the Command Server from withing an Event Server isntall? Do you have a long Idle setting in the mercator.ini file?
 
The problem recently was investigated on the machine and it was detected that Mercator 6.7 reads the mercator.ini faulty. This is hopefully the main cause for the mentioned start latency and a correction should bring up a fix for all Mercator users.
Time stamping would not help as this indicates the pure mapping time, and does not include the start time of a command server instance.
You will not detect the problem as a major issue if using an Event Server or Launcher as these load the mercator.ini once and then process maps via API from the started instance. Only command server calls will read the mercator.ini for each call resulting in long execution times.

 
I just ran a series of test using the example sinkmap provided with the install on HPUX11. Averal execution time was .0405 seconds. I saw no delay and I checked reported incidents and see nonthing about mis-reading mercator.ini

Do you have an SCase number?


BocaBurger
<===========================||////////|0
The pen is mightier than the sword, but the sword hurts more!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top