×

Loading...
Ad by
  • 推荐 OXIO 加拿大高速网络,最低月费仅$40. 使用推荐码 RCR37MB 可获得一个月的免费服务
Ad by
  • 推荐 OXIO 加拿大高速网络,最低月费仅$40. 使用推荐码 RCR37MB 可获得一个月的免费服务

.NET vs J2EE, which will win?

本文发表在 rolia.net 枫下论坛(ZT)

Microsoft’s Greg Leake recently penned a digest article describing a benchmark the company produced that compared a .NET server setup to an IBM WebSphere server setup. The task at hand was a stock trading application. It is hard to recall a time when a company published a benchmark competition that it lost, and this one does not break with that precedent. Leake tells us that, from past experience, he is quite aware of the cynicism that can greet such studies, but that he finds benchmarks can elicit worthwhile comments. He agrees that there can be fun and insight in the froth of remarks that usually follow benchmark publications. We offer the digest version [PDF] of the benchmark with that in mind.

The benchmark at hand seeks to compare the performance of Web services stacks using an equivalent workload and WSDL. Leake et al re-engineered IBM’s Trade 6.1 performance application to run on .NET 3.0, creating a benchmark app known as .NET Stocktrader. Details of the test beds are available in the PDF post we provide, although the really complete info is to be found in the full document on the MS site. Among the highlights [from the MS point of view]: Windows Communication Foundation running over MSMQ had 67% better throughput than the IBM WebSphere JMS/SIB message queue configuration using EJB/entity beans. Pulling EJB out of the equation and using JDBC yielded a less startling throughput differential of 16.2%.更多精彩文章及讨论,请光临枫下论坛 rolia.net
Report

Replies, comments and Discussions:

  • 工作学习 / 专业技术讨论 / .NET vs J2EE, which will win?
    本文发表在 rolia.net 枫下论坛(ZT)

    Microsoft’s Greg Leake recently penned a digest article describing a benchmark the company produced that compared a .NET server setup to an IBM WebSphere server setup. The task at hand was a stock trading application. It is hard to recall a time when a company published a benchmark competition that it lost, and this one does not break with that precedent. Leake tells us that, from past experience, he is quite aware of the cynicism that can greet such studies, but that he finds benchmarks can elicit worthwhile comments. He agrees that there can be fun and insight in the froth of remarks that usually follow benchmark publications. We offer the digest version [PDF] of the benchmark with that in mind.

    The benchmark at hand seeks to compare the performance of Web services stacks using an equivalent workload and WSDL. Leake et al re-engineered IBM’s Trade 6.1 performance application to run on .NET 3.0, creating a benchmark app known as .NET Stocktrader. Details of the test beds are available in the PDF post we provide, although the really complete info is to be found in the full document on the MS site. Among the highlights [from the MS point of view]: Windows Communication Foundation running over MSMQ had 67% better throughput than the IBM WebSphere JMS/SIB message queue configuration using EJB/entity beans. Pulling EJB out of the equation and using JDBC yielded a less startling throughput differential of 16.2%.更多精彩文章及讨论,请光临枫下论坛 rolia.net
    • .NET will.
    • Both will die. For sure.
      • J2EE will die earlier.
        • Not likely. MS is messing COM+ (the best product from MS IMO) with .NET, and EJB3 may correct the mistakes made in EJB2. Anyway, I was really surprised when hearing that OLG is using Websphere...
          • take it in a different way, MS is creating more jobs...which is good.:D
        • whichever supports pascal or python will survive! :DDD
    • WIN-WIN