Differences

This shows you the differences between two versions of the page.

--- linuxperf [2024/11/30 09:39] – [Flowchart to tie all toghether] dani
+++ linuxperf [2024/11/30 12:27] (current) – [Get on Top of it] admin
@@ Line 7: / Line 7: @@
 Linux's top command provides a wealth of troubleshooting information, but you have to know what you're looking for. Reference this diagram as you go through the steps below:
-{{:images:top.png?direct&400|Top output}}
+{{:images:top.png?direct&600|Top output}}
 ==== Step 1: Check I/O wait and CPU idletime ====
@@ Line 70: / Line 70: @@
 Low swap means you have a "real" IO wait problem. The next step is to see what's hogging your IO.
-{{:images:iotop.png?direct&400|}}
+{{:images:iotop.png?direct&600|}}
 ''%%iotop%%'' is an awesome tool for identifying io offenders.
@@ Line 96: / Line 96: @@
 ===== Flowchart to tie all toghether =====
-{{:images:slowserver.png?direct&600|Slow server}}
+{{:images:slowserver.png?direct&400|Slow server}}
 ===== Additional tips =====
@@ Line 120: / Line 120: @@
 ==== Memory ====
-{{:images/ramusage.png| Icinga memory usage}}
+{{:images:ramusage.png?direct&600| Icinga memory usage}}
 ==== Swap ====
-{{:images/swapusage.png| Icinga swap usage}}
+{{:images:swapusage.png?direct&600|Icinga swap usage}}
 ==== CPU ====
-{{:images/cpuusage.png| Icinga CPU usage}}
+{{:images:cpuusage.png?direct&600|Icinga CPU usage}}
-{{:images/iowaits.png| Icinga I/O waits}}
+{{:images:iowaits.png?direct&600|Icinga I/O waits}}
-{{:images/blockedpocesses.png| Icinga blocked processes}}
+{{:images:blockedpocesses.png?direct&600|Icinga blocked processes}}
 ==== Network ====
-{{:images/netusage.png| Icinga network usage}}
+{{:images:netusage.png?direct&600| Icinga network usage}}