The trade data is "weighed" and a fee is collected for each kilobyte.
对交易数据“称重”，按每千字节收费。
Performance improvement between 4-kilobyte pages and other supported page sizes
KB页面与其他受支持的页面大小之间的性能提升
The cost of storing or transmitting a kilobyte of data really is now too cheap to meter.
存储和传递一千字节数据的成本现在便宜到可以忽略不计，这种事情真的在发生。
Performance improved of 5% with the 64-kilobyte pages as compared to the 4-kilobyte pages.
与使用 4KB 的页面相比，使用 64KB 的页面可以使性能提高 5%。
As shown in Chart 2, with 64-kilobyte pages, the DB2 workload's CPI metric improved by 11%.
如图2所示，使用64KB页面时，DB 2工作负载的CP i度量提高了11%。
We discuss the performance benefits of using 64-kilobyte pages with DB2 later in this paper.
我们将在本文的后面讨论对DB 2使用64KB的页面所带来的性能优点。
Starting with DB2 9, DB2 automatically detects and USES 64-kilobyte page sizes for select memory regions.
从DB 29开始，DB 2自动为选择的内存区域检测和使用64KB页面大小。
In fact, most workloads will likely see a benefit by using 64-kilobyte pages rather than 4-kilobyte pages.
实际上，对于大多数工作负载，使用64KB的页面比使用4KB的页面更好。
There was a performance improvement of 13% with the 64-kilobyte page size in comparison to the 4-kilobyte pages.
当使用64KB页面大小时，与使用4 KB页面大小相比，在性能上提高了13%。
Data is optimized for the tablet, so as the company explains, a 3-megabyte image may be crunched into a 50-kilobyte file.
数据会为了这款平板电脑而进行优化处理，因此正像公司所解释的，一幅3 MB的图像可能被压缩成50k的文件。
Note that 64-kilobyte pages are fully capable of being paged and that the size of the pool of 64-kilobyte page frames is dynamic.
注意，64KB页面完全可以进行分页，并且64 kb页帧的池的大小是动态的。
In recent days, increasing volumes of data and processor-addressable memory has rendered the 4-kilobyte page size somewhat ineffective.
最近，随着数据量和处理器可寻址内存的增加，4KB的页面大小的效率变得有些低下了。
Ext2fs is designed for block devices like IDE devices, where the logical block size will be on the order of 512 bytes, 1 kilobyte, and so on.
Ext2fs是为象ide设备那样的块设备设计的，这些设备的逻辑块大小是512字节，1 k字节等这样的倍数。
Although 16-gigabyte pages are intended only for use in very high performance environments, 64-kilobyte pages are designed for general purposes.
GB的页面仅用于性能非常高的环境，而64KB的页面则是为通用目的而设计的。
The TLB miss rate decreased by 13% compared to the same measurement for 4-kilobyte pages, thereby improving the overall performance of the workload by 13%.
与使用4KB的页面相比，tlb失误率减少了13%，导致工作负载的整体性能提高13%。
The above example jumps back to the beginning of a file. If you don't want to go back quite all the way -- let's say a kilobyte into it -- then you just write
以上示例将跳转回文件的开头。
DB2 9 automatically detects and USES 64-kilobyte page sizes when running on the latest AIX 5l V5.3 TL04 operating system on a system that supports this page size.
当在支持64KB页面大小且采用最新的AIX5lV5.3TL 04操作系统的系统上运行时，DB 29会自动检测和使用64 KB页面大小。
With the help of the Charts 1 and 2, you can easily infer that the use of 64-kilobyte page sizes provides significant performance improvement for DB2 applications.
通过图1和图2很容易推断，使用 64KB的页面大小可以明显提高DB2应用程序的性能。
The AIX 5l operating system fully manages the pool size and varies the number of 4-kilobyte and 64-kilobyte page frames to meet demand for the different page sizes.
AIX5l操作系统管理池的大小，并根据不同页面大小的需要改变4KB和64kb页帧的数量。
Prior to this release, DB2 used the 4-kilobyte page size by default and also provided the ability to custom-configure 16-megabyte pages on systems that supported it.
在此版本之前，DB 2默认情况下都是使用4 KB的页面大小，同时在支持16MB页面的系统上提供了自定义配置16 MB页面的能力。
It is not necessary to pin the 64-kilobyte pages in memory and the AIX 5l operating system dynamically moves pages between 4-kilobyte and 64-kilobyte page-size pools.
这里完全没有必要将64KB页面固定在内存中，AIX5l操作系统可以动态地移动4KB和64 KB页面大小的池之间的页面。
DB2 supports all the page sizes (4-kilobyte, 64-kilobyte, 16-megabyte, and 16-gigabyte) that are available with the underlying system for its buffer-pool-shared memory region.
DB 2支持缓冲池共享内存区域使用底层系统上可用的所有页面大小(4KB、64KB、16 MB和16 GB)。
Do this with extreme caution, because over configuring the system with 16-megabyte or 16-gigabyte pages can lead to excessive paging of 4-kilobyte or 64-kilobyte page size pools.
这时要特别小心，因为如果配置不当，则可能导致4KB或64 KB页面大小的池过度分页。
Chart 1 shows the relative performance improvements, which was normalized between the 4-kilobyte page size and the different page sizes that DB2 and the AIX 5l operating system support.
图1展示了相对的性能提高，它们是在4KB页面大小与DB2和the AIX5l操作系统所支持的不同页面大小之间进行规格化之后得到的。
In addition to all DB2 Shared memory regions, DB2 9 automatically USES 64-kilobyte pages for its process stack, thereby giving further performance improvements without any resource overhead.
除了所有DB2共享内存区域外，DB 29还为它的进程栈自动使用64kb页面，从而进一步提高性能，同时又不带来任何资源开销。
When running the 64-bit AIX 5l kernel at the 5300-04 technology level on POWER5 + processor-based systems, support for 64-kilobyte page sizes is automatic, requiring no system configuration or tuning.
当在基于POWER 5 +处理器的系统上运行5300-04技术级别的64位AIX5l内核时，对64KB页面大小的支持是自动启用的，不需要进行系统配置或调优。
When running the 64-bit AIX 5l kernel at the 5300-04 technology level on POWER5 + processor-based systems, support for 64-kilobyte page sizes is automatic, requiring no system configuration or tuning.
当在基于POWER 5 +处理器的系统上运行5300-04技术级别的64位AIX5l内核时，对64KB页面大小的支持是自动启用的，不需要进行系统配置或调优。
应用推荐