RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 639780 - Performance Tuning Guide: TRACKING BUG for [CPU] [NUMA and multi-core support]
Summary: Performance Tuning Guide: TRACKING BUG for [CPU] [NUMA and multi-core support]
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Deadline: 2012-01-06
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Performance_Tuning_Guide
Version: 6.2
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Laura Bailey
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 639779
TreeView+ depends on / blocked
 
Reported: 2010-10-04 02:19 UTC by Don Domingo
Modified: 2012-03-07 04:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-07 04:30:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
First draft of section 4.1 CPUs and NUMA Topology (8.26 KB, text/plain)
2011-04-01 20:18 UTC, Clark Williams 		no flags Details
first draft of section 4.2 NUMA and multi-core support (3.97 KB, text/plain)
2011-07-06 15:20 UTC, Clark Williams 		no flags Details
NUMA topology diagram (12.06 KB, application/vnd.oasis.opendocument.graphics)
2011-08-29 17:52 UTC, Clark Williams 		no flags Details
NUMA paper and charts used (Shak/Tim/Larry/Rik/Peter/Andy) (38.29 KB, application/vnd.oasis.opendocument.text)
2011-09-06 15:22 UTC, John Shakshober 		no flags Details
View All

Comment 13 Clark Williams 2011-04-01 20:18:04 UTC 
Created attachment 489493 [details]
First draft of section 4.1 CPUs and NUMA Topology

Initial draft of section 4.1
Comment 14 Laura Bailey 2011-04-05 01:31:12 UTC 
Clark, I commented on BZ 641009 about the content you've attached here. :) Thanks.

Draft content for the "NUMA and multi-core support" section has not been received, though. Any idea of a date for this?
Comment 15 Clark Williams 2011-04-05 15:07:39 UTC 
Still working on NUMA and multi-core. possibly this week
Comment 18 Clark Williams 2011-07-06 15:20:45 UTC 
Created attachment 511511 [details]
first draft of section 4.2 NUMA and multi-core support

Initial draft of section 4.2
Comment 30 Clark Williams 2011-08-29 17:52:03 UTC 
Created attachment 520442 [details]
NUMA topology diagram

I'm not sure I like the example of numa topology in sectin 4.2:

"The performance of a NUMA system can be improved primarily by ensuring that information travels efficiently. To do so, you must be aware of your system's topology - the CPUs, the memory banks, and the paths between them. The numbered servers in Figure 4.1, “An example of NUMA topology” represent the CPUs and memory banks of a system, and the paths between them represent the interconnects between those CPUs and memory banks. If an application's code resides on memory bank 1, and CPU 2 wants to execute that code, then the most efficient path is 123."

This example doesn't really make sense with the diagram given. There are six servers shown in the diagram and if you assume that there is one core and one memory bank per server, then if "CPU 2 wants to execute that code" (on bank 1) then it's one hop between 1 and 2; 3 is not a component of that access path. 

I'm no graphic artist, but attached is a quick-n-dirty representation of a two node NUMA system with 4 cpus per node and one memory bank per node. In this example system, any cpu on node 1 has direct access to the memory on that node. If any cpu on node 1 wants to access the memory on node two it has to go through the node 2 controller, meaning that the access takes at least twice as long.
Comment 32 John Shakshober 2011-09-06 15:22:14 UTC 
Created attachment 521689 [details]
NUMA paper and charts used (Shak/Tim/Larry/Rik/Peter/Andy)

Feel free to use openoffice paper and graphs to describe NUMA in RHEL6 and performance improvements.
Note You need to log in before you can comment on or make changes to this bug.