The following table illustrate (in secs) the time required to execute 100 transsactions under different scenarios: web service vs different forms of remoting (HTTP/binary, HTTP/XML and TCP/binary). The baseline states the amount of time required to execute the same transactions without any remoting or web services-related overhead.
Environment is W2K Server with everything (end-to-end) running on the same machine. TRX1 has small amount of input and output data. TRX2 has a medium amount of output data. The same exercise was repeated under different IIS setups from the security standpoint: anonymous vs Integrated Windows Auth (IWA). Type Security Setup TRX1 TRX2 WebService Anonymous 9,273 29,142 IWA 80,246 108,386 Remoting HTTP/BIN Anonymous 3,315 30,444 IWA 75,328 106,713 Remoting HTTP/XML Anonymous 4,647 50,683 IWA 81,427 123,067 Remoting TCP/BIN Anonymous 3,094 33,278 BaseLine 2,433 18,797 These numbers include execution times *only*. That is, proxy-related construction and destruction are excluded. Although these numbers do not contradict (IMO) similar reports that have been done by others (Ingo?), I think that, considering the baseline, the IWA numbers are quite unacceptable. Further research revealed that each trx request includes three round-trips between proxy and the server. I then looked at the archives and found that other people reported the same problem with no satisfactory answers (beta timeframe). Apparently the problem remains with the RTM code. Comments anoyone? Rgds, Manuel Patrone You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
