I have already written about how to use processor affinity to restrict a process and run it only on a specified central processing unit (CPU) under Linux.
This document talks about setting Processor affinity on AIX.
From the article:
Processor affinity is a facility provided by operating systems, and you can use it on multi-processor hardware. All the threads within the process can be bound to run on the specified processor. Using process affinity settings to bind or unbind threads can help you find the root cause of troublesome hang or deadlock problems, especially for those hairy deadlocks and hangs that are hard to debug.
Regardless of what system you use and what functional and regression testing you do when your application is deployed for production, you can still get errors that are unavoidable. You might get a hang where the CPU is being used 100 percent of the time, or you might get deadlocks where a couple of threads are locked and never release a resource. In some cases, you’ll see hangs in the application that are very old (even a couple of decades back), even on multiprocessor architectures and fast hardware.
Processor affinity on AIX [ibm.com]
🐧 0 comments... add one ↓
|Category||List of Unix and Linux commands|
|Disk space analyzers||df • ncdu • pydf|
|File Management||cat • cp • mkdir • tree|
|Firewall||Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04|
|Network Utilities||NetHogs • dig • host • ip • nmap|
|OpenVPN||CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04|
|Package Manager||apk • apt|
|Processes Management||bg • chroot • cron • disown • fg • jobs • killall • kill • pidof • pstree • pwdx • time|
|Searching||grep • whereis • which|
|User Information||groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w|
|WireGuard VPN||Alpine • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04|