I have a Windows service running on the server. It allows client workstations access it via .Net remoting. The Server service is simply a gateway to the database. Clients call methods on the Server class via remoting to make database calls (Selects, Inserts
During load testing we've observed the calls to the server take longer when multiple clients make simultaneous requests. The analysis indicates the requests are actually getting queued up. If 2 clients call the same method on the Server object, the two requests
are processed in sequence. We have tried both Singleton and Singlecall. Same results.
Is there a bug in .Net remoting that it cannot process simultaneous client requests? If yes, is there a workaround (a quick one)?
We are using .Net 2.0 and are willing to switch to a higher version if the bug has been resolved in 3.0 or 4.0.
View Complete Post