因为最小块大小是16字节，那么只分配链表节点的用户程序就会遭受额外的100%的开销。
Since the minimum chunk size is 16 bytes, user programs allocating only list nodes suffer 100% overhead.
读取器/写入器有性能开销，因为它们旨在用于字符流，且会在后台将数据编码为字节。
There is a performance overhead involved with readers/writers because they are intended for character streams, and they encode data to bytes under the covers.
将一个点表示成ST _ point值会增加一些开销，但是我们谈论时仍然当作是几个字节。
Representing a point as an ST_Point value adds some overhead, but still we are only talking about a few bytes.
尽管如此，最小16字节至少是任何需要8字节对齐，存在malloc薄记开销的系统的一个特性。
However, the 16 bytes minimum at least is characteristic of any system requiring 8-byte alignment in which there is any malloc bookkeeping overhead.
服务器还能限制Write布局的字节范围，以避免配额限制或减少分配开销等等。
A server can also restrict the byte range of a Write layout to avoid quota limits or to reduce allocation overhead, among other reasons.
内存开销大约为(M +B)个字节(每个内存块开头的指针忽略不计)。
The overhead averages about (m + b) bytes (ignoring the Pointers at the beginning of each memory block).
实际上，如果字节码修改的开销很大，那么对经过修改的类进行缓存有很大的好处，因为变换只需要执行一次。
Indeed, if the bytecode modification is expensive, caching the modified classes has an even greater benefit, as the transformation only ever needs to be performed once.
这通常开销非常大，因为运营商通常是按照传输的字节数进行收费的。
This is usually expensive since the operator will generally charge by the number of bytes transferred.
若必须处理许多兆字节的XML文档，花费内存、磁盘空间和CPU开销来操作这么大的文档通常是不实际的。
If you must deal with many-megabyte XML documents, it's often impractical to spend the memory, disk space, and CPU overhead to manipulate such huge documents.
这样开销从2MB 变为 2,048个字节。
This translates to only 2,048 bytes of overhead instead of 2 MB.
回想一下，B3字节覆盖路径开销和有效载荷部分。
Recall that the B3 byte covers the path overhead and payload section.
小型传输，开销很小(固定长度的头部是2字节)，协议交换最小化，以降低网络流量。
A small transport overhead (the fixed-length header is just 2 bytes), and protocol exchanges minimised to reduce network traffic.
这个数字产生通道接口接受的解决办法，因为（例如）在STS - 3的每个STS - 1的路径开销和B3字节。
This number produces acceptable resolution for a channelized interface because, (for example) each STS-1 in an STS-3 has a path overhead and B3 byte.
这些特征的代价仅为每帧3字节的额外开销，链路建立是的一些协商帧，以及一些复杂的实现。
The price we pay for all these features is 3 bytes of additional overhead per frame, a few frames of negotiation when the link is established, and a more complex implementation.
在32 位平台上，这种开销目前为 12 个字节，外加每维8 个字节。
On a 32-bit platform, this overhead is currently 12 bytes plus 8 bytes for each dimension.
内存开销非常小：基本上每个接口需要额外4个字节（对象实例数据里虚函数表指针），加上引用计数的4个字节。
Overhead in memory is very small: You basically have a 4- byte overhead per interface (the vtable pointers in the object's instance data) plus 4 bytes for the reference counter.
ST16C 554工作在FIFO模式，采用中断方式收发数据，并有16字节的硬件接收发送缓冲区，降低了CPU的开销。
ST16C554 works in FIFO mode, receives and transmits data by (interrupt) mode with a 16 byte hardware transmit buffer, that will also greatly cut down the load on the CPU.
为了从传感器获得的10位字节消耗了相当可观的数据开销(图2)。
To get just 10 bits out of the sensor involves considerable data overhead (Figure 2).
为了从传感器获得的10位字节消耗了相当可观的数据开销(图2)。
To get just 10 bits out of the sensor involves considerable data overhead (Figure 2).
应用推荐