Posts

Showing posts from April, 2018

Understanding Linux CPU Load - when should you be worried?

Image
Understanding Linux CPU Load - when should you be worried? BY ANDRE You might be familiar with Linux load averages already. Load averages are the three numbers shown with the  uptime  and  top  commands - they look like this: load average: 0.09, 0.05, 0.01 Most people have an inkling of what the load averages mean: the three numbers represent averages over progressively longer periods of time (one, five, and fifteen minute averages), and that lower numbers are better. Higher numbers represent a problem or an overloaded machine. But, what's the the threshold? What constitutes "good" and "bad" load average values? When should you be concerned over a load average value, and when should you scramble to fix it ASAP? First, a little background on what the load average values mean. We'll start out with the simplest case: a machine with one single-core processor. The traffic analogy A single-core CPU is like a single lane of traffic. Imagine you are...

Reasons why VLOOKUP is not working

1.  VLOOKUP Cannot Look to its Left What this means is if the data you are matching for is not in the left side column,  i.e. you want to match a data which is in 2nd column and 1st column value is required to be displayed then It will not be working. Solution: 1. Keep the matching column in first or left most column of the table/selection area. 2.  The solution to this involves not using VLOOKUP at all. Using a combination of the INDEX and MATCH functions of Excel is a common alternative to VLOOKUP. It is far more versatile. 2.  Your Table Contains Duplicates Ok, so your list should have duplicates. In this case a VLOOKUP is not what you need. A PivotTable would be perfect to select a value and list the results instead. 3. The Table has got Bigger update your table reference Source:  https://www.ablebits.com/office-addins-blog/2014/04/09/why-excel-vlookup-not-working/