Maximum Threads

We are also on 3.8.1P on W2k, but with 1.5GB quad CPU and 2GB memory.

We split into 3 sites when we were nearing 40 threads in one site.  We have 3 sites, 12 processes and 49 threads.  Our peak message throughput is around 160,000 per day.  Our CPU usage rarely goes over 20%.

We were told by McKesson that W2K is only ‘certified’ for a peak throughput of 250,000 messages, after that Unix must be used.  We will be very close to 250,000 toward the end of next year; because of this, we will be adding an additional production W2K server early next year.  

We were also told that once you upgrade to the 5.x platform that on W2K you must have 1GB memory per processor, so we will need to upgrade our production server before we can do that.

Seems to me that there used to be a problem on windows if the number of users on the raima database exceeded a certain number — 120, it think it was.  This may be part of the problem…I am sketchy on the details since my experience is limited to AIX and HPUX, but that might spark someone else’s memory (might also be a red herring…LOL).

Don,

From what you said “running 40 threads and 38 engines”… that is just barely over 1 thread per process.  Is that correct?  If so, I imagine your processes are working very hard with interprocess communication.  Where it makes sense, I recommend consolidating your threads into fewer processes, keeping threads on a route in the same process, if at all possible.

Debra,

I am curious.. a peak throughput of 250K messages per… hour? day?

what is the time period?

The 250,000 messages is per day.

Scott is correct.  The issue has been resolved in our most recent releases of Cloverleaf.

The limit was on Windows based systems.  The limit is 128 total threads per server.  Let me clarify the way these are counted.

Each thread counts as one user.  These include command and xlate threads too.  So if you had a process with 10 protocol threads your total would be 12.  Add these up among all your sites and see if you exceed this amount.

This was resolved as of 5.2.1 Rev 2.