当您初次登录到 developerWorks 时，将会为您创建一份概要信息。您在 developerWorks 概要信息中选择公开的信息将公开显示给其他人，但您可以随时修改这些信息的显示状态。您的姓名（除非选择隐藏）和昵称将和您在 developerWorks 发布的内容一同显示。

所有提交的信息确保安全。

当您初次登录到 developerWorks 时，将会为您创建一份概要信息，您需要指定一个昵称。您的昵称将和您在 developerWorks 发布的内容显示在一起。

昵称长度在 3 至 31 个字符之间。您的昵称在 developerWorks 社区中必须是唯一的，并且出于隐私保护的原因，不能是您的电子邮件地址。

所有提交的信息确保安全。

My developerWorks:

我的通知：

退出

选择语言：

XML and Java technologies: Document models, Part 1: Performance

A look at features and performance of XML document models in Java

Return to article

Average versus best times

The charts shown in the Java document-model performance article use the best time measured for each test. The test program also computes average times, but the average times tend to vary a lot more than the best times depending on the documents used, the number of test passes, and the order of the documents.

The two figures below show how the average times for one test run compared with the best time results for the same test run. The average time values use the default test program settings, which exclude the first pass of each test on each document. The first pass time is usually much higher than the average time, due to HotSpot optimization behavior.

Figure 1. Average document build time
Document build time chart

Figure 2. Best document build time
Document build time chart

Note that the scales differ in these charts, with the average times generally about 20% to 30% higher than the best times. The relative performance of the different models is about the same, though, no matter whether average or best time is used for the comparison.

Return to article

My developerWorks:

我的通知：

选择语言：

技术主题

软件下载

社区

技术讲座

XML and Java technologies: Document models, Part 1: Performance

分享此页面：

分享此页面：