{"id":13,"date":"2012-11-28T02:08:02","date_gmt":"2012-11-28T02:08:02","guid":{"rendered":"http:\/\/pages.charlotte.edu\/mark-hamrick\/?p=13"},"modified":"2012-11-28T02:08:02","modified_gmt":"2012-11-28T02:08:02","slug":"details-details-microprocessor-details","status":"publish","type":"post","link":"http:\/\/pages.charlotte.edu\/mark-hamrick\/blog\/2012\/11\/28\/details-details-microprocessor-details\/","title":{"rendered":"Details, Details, Microprocessor Details\u2026\u2026"},"content":{"rendered":"<p>It is the small stuff that can problematic.\u00a0 I have a system with four AMD Opteron 6272s.\u00a0 This gives us a total of 64 cores.\u00a0 During testing using an OpenMP based program doing integer operations all 64 cores came up to speed.<\/p>\n<p>However, during another program which required floating point calculation, things suddenly ground to a halt.\u00a0\u00a0 A quick look at the diagram in the article below shows the issue.<\/p>\n<p><a href=\"http:\/\/www.anandtech.com\/show\/4955\/the-bulldozer-review-amd-fx8150-tested\/2\">http:\/\/www.anandtech.com\/show\/4955\/the-bulldozer-review-amd-fx8150-tested\/2<\/a><\/p>\n<p>The Bulldozer architecture pairs two cores together.\u00a0 The issue is that those two cores share a floating point scheduler.\u00a0 So when doing floating point calculations, the two cores act as one.\u00a0 Therefore you end up with 32 Cores instead of 64.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It is the small stuff that can problematic.\u00a0 I have a system with four AMD Opteron 6272s.\u00a0 This gives us a total of 64 cores.\u00a0 During testing using an OpenMP based program doing integer operations all 64 cores came up to speed. However, during another program which required floating point calculation, things suddenly ground to [&hellip;]<\/p>\n","protected":false},"author":22,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-13","post","type-post","status-publish","format-standard","hentry","category-updates"],"_links":{"self":[{"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/posts\/13","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/users\/22"}],"replies":[{"embeddable":true,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/comments?post=13"}],"version-history":[{"count":3,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/posts\/13\/revisions"}],"predecessor-version":[{"id":17,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/posts\/13\/revisions\/17"}],"wp:attachment":[{"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/media?parent=13"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/categories?post=13"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/tags?post=13"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}