Kevin English

BLOCKSIZE should be set to 8912 (well that is what we configured ours to).

If it weren't for the screen shot, I would have assumed it was a typo. Certainly it should be 8192, or some other multiple of the OS block size, shouldn't it?
--
Kevin English

i guess another possibility for being multi threaded is having the server process handle multiple client connections simultaneously. If that's the case, then you should probably ignore my previous post.
--
Kevin English

Ross,
I'm going to go out on a limb here and hazard a guess based on the way I know that a similar tool works. Any performance issues will almost certainly be SQL Server related and not PRO-IV related,
except possibly in the way that PRO-IV creates sql stmts. So choosing the configuration that makes SQL Server run the best will probably be your best choice. 60 users is not really very many and doesn't really say anything about the number of transactions typically performed. I can't comment on what will make SQL Server perform the best. I'd be surprised if your users could tell the difference between your 2 possible configurations.

I'm interested in what way is PRO-IV multi-threaded. What do the different threads do? I can envision a thread that reads network requests from the client and a thread that does the server side processing, but what else can be separated into threads? You can't run 2 separate functions at the same time in 2 different threads, can you?
--
Kevin English

ProIV Support response: "The message is produced when a call to malloc fails when trying to acquire memory from the OS for file control structures".

If malloc is failing, then PRO-IV is either leaking memory or trashing memory during the gen process. A simple ps will show if memory is leaking. Finding out if it is trashed probably can only be done with PRO-IV support help. Good luck.
--
Kevin English

Can you post some output from vmstat while your test is running?
--
Kevin English