Laszlo Bock, SVP, Google, ‘People Operations,’ recently spoke about staff retention and what it takes to make employees happy, so they’ll stay with you. Even at the pre-eminent purveyor of perks, Google knows that these perks are not what keep people around. According to Bock, the important factors are two: working with terrific people and knowing that what they do each day matters.
Following a hockey puck can be challenging. It moves really fast and it’s not always obvious what the next player is going to do. Wayne Gretzky famously said: “Skate to where the puck is going; not where it’s been”. The same analogy can be applied in most sports: football quarterbacks throw to where the receiver is going to be; not where they are. Your monthly 4-Hour Rolling Average (and resulting MLC) is also a moving target.
By now, many shops are using soft caps and/or taking advantage of special pricing offerings from IBM such as Mobile and zNALC. These are excellent ideas — but, as all performance and capacity professionals know, reducing one 4HRA bottleneck only creates another.
A guest post by Denise P. Kalm – Most tech support people have years in the business, learning both on-the-job and in school. Many have been developers or long-time users of a product. But it takes more than just knowledge to do this job.
It requires the skills of a detective, with a relentless desire to get to the solution. It takes people skills and the desire to help others. In IT, we know the latter is more of a rare commodity. We rely on these people and simply expect them to be there for us. And they are.
Money is tight at most companies these days. Every dollar is examined and squeezed to make sure none are wasted. But there are two exceptions to the rule. Emergencies loosen purse strings. When a quick response to a security breach is required, for example, money flows. The second exception occurs when you’re first hired or transferred into a performance role. Opportunities for purchasing software don’t come along very often, so it is wise to exploit these times.
Some sages, particularly in the distributed systems space, like to say that capacity planning isn’t necessary anymore. Hardware is cheaper and virtualization makes better use of resources. Besides, no one seems to know how to do it these days. But the sages are wrong! In many ways, capacity planning has become much more essential, but
If you’re in performance or capacity planning, your value is interpreting data and creating plans of action for automation to exploit. Machines can only do this with a complete body of information; they don’t have your intuition, your experience, or your‘sense of the system’ – that intangible sense we develop as we understand our hardware and software at a deep level. This is the good stuff, the work that makes life interesting.
A properly tuned and conducted orchestra can produce amazing sounds. One out-of-tune instrument can ruin the whole performance. Your mainframe is no different. A well architected and tuned system can support thousands of users and applications with sub-second response. But it only takes one small parameter or threshold to be exceeded and the whole system feels like it’s grinding to a halt.
There is no shortage of available metrics to provide detailed insight into system performance. The problem is sorting through them all and recognizing what’s important. Utilization, for example, comes in many forms. Hiperdispatch can make or break performance, and processor cache… well, a faster CPU won’t help you with a cache miss. This session will discuss these and other key performance areas to watch, what to look for, what to ignore, and what… well, as they say – it depends.