|
Check the working set specified for the created processes, and check
the process quotas for sufficient values, and check for sufficient
free memory on the system, etc.
If there are no quotas specified in the call to sys$creprc or lib$spawn,
seriously consider adding the list of(minimum) required quotas -- one
inherits the SYSGEN minimum and/or default values, which may or may not
reflect specific application requirements.
Also note that lib$spawn is traditionally a slow operation, and more
particularly slow when large numbers of symbols and logical names
are copied into the context of the subprocess.
If nothing obvious shows from the above checks, you will likely want
to characterize where the application is spending its time and compare
these timings with the VAX implementation of the application, using
some simple application-specific profiling and/or logging tools.
(Imbeded calls to lib$show_timer, et al., at the simplest, or some
slightly more advanced logging and debug-tracing support.) (Without
this profiling information, we're all guessing...)
|
| If the spawned subprocesses are running images which require a lot
fo shareable images to be mapped at image activation time, then this
might be the problem. Image activation can sometimes be slower on Alpha
with lots of shareable images, but once things get going, you should
see the speed increase. There are also some things you can do to speed
this up, but I know there's at least one note in here that talks about
image activation times.
|