根元素通常粗略地确定了文档大小。
The root element generally determines the rough size of the document.
让我们看看清单1中的基本文档大小。
Let's take a look at the sizes of the base documents in Listing 1.
这会减少所需，但会增加的HTML文档大小的HTTP请求的数。
This reduces the number of HTTP requests that are needed, but increases the size of the HTML document.
移动设备上的W3CCSSOM：这些测试覆盖了屏幕大小、鼠标位置、文档大小和滚动位置等。
Mobile W3C CSSOM - Covers aspects like screen size, mouse position, document size, and scroll offset.
尽管如此，在交换的文档大小适中的情况下，这样的处理速率对于单线程应用程序来说仍然令人吃惊。
Even so, that rate is impressive for a single threaded application given the comparative size of the document being exchanged.
当objectstore相对于文档数量和文档大小来说不是很大时，数据库存储区域比较有用。
Database storage areas are useful when the size of your object store is not very large in terms of number of documents and the sizes of those documents.
经验法则是，为XML数据选择一个不小于平均预期文档大小的两倍而且不超过32KB最大值的页宽。
As a rule of thumb, choose a page size for XML data which is not smaller than two times your average expected document size, subject to the maximum of 32kb.
硬盘空间回收器，它能够显露文档大小和实际占空间数及其浪费的空间等，让你做出相应的删除决定。
Hard disk space recovery, which will show the actual size and the number of its total waste of space, space, let you make the decision to delete the corresponding.
如果一个文档大小超出了一个页面，每个文档分成的子块的数量取决于页宽(4kb、8kb、16kb或32kb)。
If a document does not fit on a page, the number of splits per document depends on the page size (4kb, 8kb, 16kb, or 32kb).
一个使用expat构建的应用程序在读取这么大的XML时可以只提取少部分感兴趣的标记，使用的命令占用的内存比文档大小小得多。
An application built around expat is happy to pull off a few tags of interest as it reads through that much XML, likely utilizing orders of magnitude less memory than the document size.
原生xml数据库优于非数据系统的第二个长处是文档的大小。
The second advantage that native XML databases have over non-database systems is document size.
内联功能可以显著减小区域索引的大小，因为内联文档不需要任何区域索引条目。
Inlining can reduce the size of the regions index dramatically since inlined documents do not require any regions index entries.
不过，指出这一点并没有很大意义，因为重组元素内容大于块大小的文档并不合理(而且通常不应该执行)。
However, there is little point in lifting this, since reorganization will be inconsequential for documents with element contents larger than the block size (and should not be performed in general).
使用字节索引值来代替标记的策略在某种程度上减少了重新构造后的文档的大小，但也限制算法只能处理不同标记数少于254的DTD。
The strategy of using byte index values in the place of tags reduces the size of restructured documents somewhat, but also limits the algorithm to handling DTDs with fewer than 254 distinct tags.
除了新的工作负载之外，我们在用户的邮件文件中放置了3,000个不同大小的文档。
In addition to the new workloads, we now have users start with 3,000 documents of various sizes in their mail files.
在正常的测试负载中，还不能证明数据库中的文档的大小和数量会对性能产生确切的影响。
The size or the total number of documents in the database did not prove to be an accurate predictor of the performance impact, under normal test loads.
它具有很多内置的比较算法，并且能够基于文档内容和大小自动地选择算法。
It has many built-in comparing algorithms and has the ability to automatically choose algorithms based on the document content and size.
注意：用于测试的文档的大小不会对平均响应时间产生很大的影响，但得出的结果有很大差别。
NOTE: the size of the document being used for testing did not generate significant differences in average response times, but we did see greater variance in results.
文档缓存大小。
最后，图3显示了每种框架在表示文档时所使用的内存大小。
Finally, Figure 3 shows the memory used by each of the frameworks to represent the documents.
订单文档的大小是1KB到2KB。
通常，根据所用文档的大小不同，xml框架的相对性能会有巨大差异，因此在这些性能测试中，我同时包含了大文档和小文档。
Often, the relative performance of XML frameworks differs greatly depending on the size of documents being used, so I included both large and small documents in these performance tests.
上传文档的大小被限制为0字节到1兆字节。
The size of the uploaded document is limited between 0 bytes and 1 Megabyte.
如果XML文档的大小小于页面大小，那么就可以与另外的SQL元素同时存储。
If the XML document is small enough to fit into the page size, it can be stored with the other SQL elements.
这些数据集包含从2KB到 100MB的各种大小的文档。
These data sets included documents of various sizes that ranged from 2KB to 100MB.
我们发现相同大小的邮件文件使用的资源可能相差很大，这取决于文档的平均大小和数量。
We found that mail files of the same size can use significantly different resources, depending on the average size and number of documents.
基于将要分解的XML文档的大小，该存储过程有五个变种。
There are five variations of this stored procedure based on the size of the XML document to be decomposed.
由于减少了内存需求，事件API可以处理任意大小的文档，包括大小超过可用内存的文档。
Because their memory requirement is reduced, event APIs enable processing documents of any size, even documents greater than the available memory.
由于减少了内存需求，事件API可以处理任意大小的文档，包括大小超过可用内存的文档。
Because their memory requirement is reduced, event APIs enable processing documents of any size, even documents greater than the available memory.
应用推荐