Creating 150 objects locally wouldn't be a problem for a modern computer, but the latency involved creating an object remotely is considerable (relatively). Although I have no figures for how many you should expect to be able to create reliably over a LAN simultaneously, I think 150 is pushing it a bit.
I do know that most stress test tools recommend that you only have 100 threads running at once to make remote calls. If you want to run more, you have to use multiple clients. It is certainly not an issue with .NET/DCOM interop as we see this behaviour with plain old COM. Try reducing the number and let us know at what point it starts working reliably. It could be that the interop layer will reduce the number of objects you can create at once, compared with a straight COM client, and I'd be interested to know if this is the case (though, I suspect most of the bottleneck is in your network, and not in the local CPU). Cheers, Andy. ******************************************************** Attachments in this message have been swept by NAIs TVD (version 4.0.4213) for the presence of known computer viruses. ******************************************************** ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. ________________________________________________________________________
