TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Data Processing: PLINQ, Parallelism and Performance

23 点作者 stsmytherie超过 14 年前

2 条评论

nathanwdavis超过 14 年前
Interesting that on a six core machine there is very little gain after a Degree of Parallelism of 3. The problem does seem highly data parallelizable (is that a word). So why isn't it able to better utilize the 6 cores?
评论 #2080468 未加载
评论 #2081300 未加载
评论 #2080355 未加载
ot超过 14 年前
From the article:<p>&#62; Each place name is represented by a UTF-8 (en.wikipedia.org/wiki/UTF-8) text line record (variable length) with more than 15 tab-separated data columns. <i>Note: The UTF-8 encoding assures that a tab (0x9) or line feed (0xA) value won’t occur as part of a multi-byte sequence; this is essential for several implementations.</i><p>What? I guess that they use a longer (2-byte?) encoding for those codepoints, but from the very same wikipedia page that they link:<p>&#62; a sequence that decodes to a value that should use a shorter sequence (an "overlong form") [is invalid]<p>...<p>&#62; Implementations of the decoding algorithm MUST protect against decoding invalid sequences<p>Are they advising to use an invalid and potentially broken UTF8 encoding?
评论 #2080405 未加载
评论 #2080296 未加载