Unfortunately, because not all of the problem can be parallelized and there's overhead in managing the processors, the speedup is quite a bit less.
不幸的是，并非所有的问题都可以并行化，而且还有管理处理器的开销，所以速度的提高并没有这么大。
To understand the implications of these new features, we need to delve into the fine art of memory management a bit and consider why allocation overhead and speed are a big deal.
为了理解这些新增功能的含义，我们需要深入研究内存管理中的艺术，并考虑为什么分配开销和运行速度是大问题。
Both feature a great amount of message overhead, and their performance is quite a bit slower than CORBA's; however, for many applications you really don't care about these factors.
两个协议的特点都是需要大量的消息开销，它们的性能要比CORBA的性能慢得多；不过，对于许多应用程序而言，您实际上并不关心这些因素。
That's a fair bit of overhead, and the interception isn't cheap at all.
这需要一定的开销，因此拦截一点都不便宜。
Also, be aware that using a 64-bit WebSphere Application Server instance has an overhead of 5% to 15% in terms of transaction throughput, compared with using 32-bit, depending on your workload.
此外注意，与使用32位相比，使用64位WebSphereApplicationServer实例在事务吞吐量方面的开销为5%至15%，具体取决于您的工作负载。
Simulation results show that compared with fixed training interval schemes, the improved algorithm can achieve better BER (Bit Error Rate) performance while keeping lower system overhead.
与采用固定训练周期相比，该方法可以在保证比较低的导频开销的同时，使系统获得更好的误比特性能。
On a 32-bit platform, this overhead is currently 12 bytes plus 8 bytes for each dimension.
在32 位平台上，这种开销目前为 12 个字节，外加每维8 个字节。
Although using a regex for this adds a bit of performance overhead, it lets you defer the list of whitespace characters to the browser for the sake of brevity and compatibility.
请注意，此方案在循环中使用正则表达式检测字符串尾部的字符是否空格，尽管使用正则表达式增加了一点性能负担，但它允许你根据浏览器定义空格字符列表，以保持简短和兼容性。
Hence having XML structure will be bit challenge as parsing, locating parent node and updating XML data will put additional overhead on programmer.
所以使用XML结构在解析、定位和更新数据时麻烦，要让程序员提前考虑很多细节。
Hence having XML structure will be bit challenge as parsing, locating parent node and updating XML data will put additional overhead on programmer.
所以使用XML结构在解析、定位和更新数据时麻烦，要让程序员提前考虑很多细节。
应用推荐