@kabrina_starr on Threads

Kabrina Starr Leaks @ On Threads

Sempre ouço pessoas falando coisas como Your kind of measurement is a good first start, but you have to dig deeper to really pinpoint the bottlenecks.

OPEN

Ou simplesmente seria uma abreviação? Any answer has to take wild guesses about your setup But the main difference between them is not cle.

@kabrina_starr on Threads

Hopping from java garbage collection, i came across jvm settings for numa

Curiously i wanted to check if my centos server has numa capabilities or not

Is there a *ix command or utility that could. The numa_alloc_* () functions in libnuma allocate whole pages of memory, typically 4096 bytes Cache lines are typically 64 bytes Since 4096 is a multiple of 64, anything that comes back from numa_alloc_* () will already be memaligned at the cache level

Beware the numa_alloc_* () functions however It says on the man page that they are slower than a corresponding malloc (), which i'm sure is. The issue here is that some of your numa nodes aren't populated with any memory I want to bind a process running inside a docker container to this numa node, but it errors out:

@kabrina_starr on Threads
@kabrina_starr on Threads

Details

Memory latency is not a concern

Is there any benefit from dividing the work between two or more cores in different numa zones Equivalently, does working across zones reduce the available bandwidth? You are asking about os numa policies without even telling us your os (version), anything about your hardware, and only extremely little about your code

@kabrina_starr on Threads
@kabrina_starr on Threads

Details

(@kabrina__starr) • Instagram photos and videos
(@kabrina__starr) • Instagram photos and videos

Details