Comments (8)
@dfaggioli Next sentence to clarify:
"What is not obvious is the links to the IO die, but it should be taken into account when splitting a workload to optimize bandwidth to memory."
"Not obvious are the links to the IO die, but this () should be taken into account .... "
"Not obvious are the links to the IO die, but the IO die should be taken into account ...."
from suse-best-practices.
@dfaggioli and one more:
In addition to lstopo can provide the information, the level, size and ID of CPUs that share cache can be identified from the files under /sys/devices/system/cpu/cpuN/cache.
Options:
"In addition to lstopo which can provide the information, the level, size and ID of CPUs that share cache can be identified from the files under /sys/devices/system/cpu/cpuN/cache."
"In addition, lstopo can provide the information, the level, size and ID of CPUs that share cache, which can be identified from the files under /sys/devices/system/cpu/cpuN/cache."
from suse-best-practices.
Hi Dario @dfaggioli
can you clarify the following sentence:This should be considered when tuning for Non-Uniform Memory Architecture (NUMA) as all memory accesses are not necessarily to local memory incurring a variable access penalty.
I think it means that it can happen that a memory operation accesses some remote (i.e., non-local) memory. That is, memory accesses not necessarily always happen to local memory, which mean they can incur a variable access penalty.
So, this, I would say:
This should be considered when tuning for Non-Uniform Memory Architecture (NUMA) as all memory accesses are not necessary to local memory incurring a variable access penalty.
However, can we double check with @gormanm , as I think this comes from him ?
from suse-best-practices.
@dfaggioli Next sentence to clarify:
"What is not obvious is the links to the IO die, but it should be taken into account when splitting a workload to optimize bandwidth to memory."
This sentence is right below the figure fig-epyc-topology
. I think it means that it is not obvious, by looking at that figure, how the various CCXs/dies (which are shown in the figure itself) are connected to the IO die (which is not present in the figure because the tool does not draw it).
But again, @gormanm would be the one source of truth here. :-)
from suse-best-practices.
@dfaggioli and one more:
In addition to lstopo can provide the information, the level, size and ID of CPUs that share cache can be identified from the files under /sys/devices/system/cpu/cpuN/cache.
Options:
"In addition to lstopo which can provide the information, the level, size and ID of CPUs that share cache can be identified from the files under /sys/devices/system/cpu/cpuN/cache."
"In addition, lstopo can provide the information, the level, size and ID of CPUs that share cache, which can be identified from the files under /sys/devices/system/cpu/cpuN/cache."
This is still from @gormanm . Personally, I'd go for something like:
"In addition to the information that lstopo can provide, the level, size and ID of CPUs that share cache can be identified from the files under /sys/devices/system/cpu/cpuN/cache."
But we should really double check with him (plus, I'm no native Eng. speaker, so don't trust me!)
from suse-best-practices.
Hi Dario @dfaggioli
can you clarify the following sentence:
This should be considered when tuning for Non-Uniform Memory Architecture (NUMA) as all memory accesses are not necessarily to local memory incurring a variable access penalty.I think it means that it can happen that a memory operation accesses some remote (i.e., non-local) memory. That is, memory accesses not necessarily always happen to local memory, which mean they can incur a variable access penalty.
So, this, I would say:
This should be considered when tuning for Non-Uniform Memory Architecture (NUMA) as all memory accesses are not necessary to local memory incurring a variable access penalty.
However, can we double check with @gormanm , as I think this comes from him ?
The switch from "necessarily" to "necessary" changes the semantics of the sentence. Alternative suggestion as follows
This should be considered when tuning for Non-Uniform Memory Architecture (NUMA) as all memory accesses may not reference local memory incurring a variable access penalty.
from suse-best-practices.
@dfaggioli and one more:
In addition to lstopo can provide the information, the level, size and ID of CPUs that share cache can be identified from the files under /sys/devices/system/cpu/cpuN/cache.
Options:
"In addition to lstopo which can provide the information, the level, size and ID of CPUs that share cache can be identified from the files under /sys/devices/system/cpu/cpuN/cache."
This version is the best.
from suse-best-practices.
@dfaggioli Next sentence to clarify:
"What is not obvious is the links to the IO die, but it should be taken into account when splitting a workload to optimize bandwidth to memory."
"Not obvious are the links to the IO die, but the IO die should be taken into account ...."
This option is the better of the two. Thanks!
from suse-best-practices.
Related Issues (20)
- [doc] Issue in "Cluster bootstrap and more" HOT 2
- [doc] Issue in "DESCRIPTION OF IMPORTANT RESOURCE AGENT PARAMETERS" HOT 2
- [doc] Issue in "Adding cluster rules for automatic shutdown of the non-replicated SAP HANA" HOT 2
- [doc] Issue in "Creating AWS EC2 Instance" HOT 2
- Request for more information / new step-by-step guide - see: https://bugzilla.suse.com/show_bug.cgi?id=1216632 HOT 7
- [doc] Issue in "Constraints" HOT 2
- [doc] Issue in "ENTRY IN SUDO PERMISSIONS /ETC/SUDOERS.D/SAPHANASR FILE" HOT 2
- SLES12-4-SAP recommended documentation change of use of SAPHanaSrMultiTarget.py versus SAPHanaSr HOT 6
- [doc] Issue in "Allowing <sid>adm to access the cluster" HOT 2
- [doc] Issue in "Microsoft SQL Server on SUSE Linux Enterprise Server" - out of date HOT 1
- [doc] Issue in "Interrupt Coalescing" HOT 1
- [doc] Issue in "Example cluster configuration" HOT 2
- [doc] Issue in "Example Cluster Configuration" HOT 4
- [doc] Issue in "Example cluster configuration" HOT 6
- [doc] Issue in "Client image configuration recommendations" HOT 1
- [doc] Issue in "Deployment" HOT 1
- [doc] Issue in "Deployment" HOT 1
- [doc] Issue in "High level overview" HOT 1
- [doc] Issue in "SAP HANA System Replication Scale-Out High Availability in Amazon Web Services" HOT 3
- [doc] Issue in "SAP HANA System Replication Scale-Out High Availability in Amazon Web Services"
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from suse-best-practices.