netconfig changes work in batches of 9, why?

[randomjoe1]

win 2003 r2 server

LMS 3.2

RME 4.3.1

When a netconfig job (and SWIM job for that matter) executes, I notice the job chages about 9 devices concurrently.  The job is set for parallel changes.  Is there a way to increase the number of concurrent modifications?  I have to make changes on ~1500 switches and have 2 hour maintenance windows (trying to maximize time efficiency and minimize outage windows).

I am doing 2 netconfig jobs, 1 is adding 2 simple configurations, the second is a reload.  the SWIM job is pretty standard.

If this is an application restriction, would creating multiple jobs to run at the same time help speed things up?

[Joe Clarke]

The number of parallel threads can be controlled.  If your server has at least 4 GB of RAM and two CPUs, you can run the RME Performance Tuning tool (NMSROOT/bin/rmept/rmeptt.{sh,bat}) to tune the server for better performance at the expense of memory and CPU resources.  This will increase the number of config download threads to 20 amonst other things.