サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
衆院選
tanelpoder.com
Do Not Use '>' in Your Command Prompt (and How to Stay Safe in Shell) Over the years of troubleshooting performance problems in the Unix/Linux world, I have seen multiple cases where a regularly used command line tool in a customer server just stops working for some reason. The tool just returns immediately, doing absolutely nothing. No output printed, no coredumps and the exit code is zero (succe
Here’s a list of reasons why SELECT * is bad for SQL performance, assuming that your application doesn’t actually need all the columns. When I write production code, I explicitly specify the columns of interest in the select-list (projection), not only for performance reasons, but also for application reliability reasons. For example, will your application’s data processing code suddenly break whe
Introduction Brendan Gregg invented and popularized a way to profile & visualize program response time by sampling stack traces and using his FlameGraph concept & tools. This technique is a great way for visualizing metrics in nested hierarchies, what stack-based program execution uses under the hood for invoking and tracking function calls. If you don’t know what FlameGraphs are, I suggest you re
RAM is the new disk – and how to measure its performance – Part 2 – Tools [ part 1 | part 2 | part 3 ] In the previous article I explained that the main requirement for high-speed in-memory data scanning is column-oriented storage format for in-memory data. SIMD instruction processing is just icing on the cake. Let’s dig deeper. This is a long post, you’ve been warned. Test Environment I will cove
Peeking into Linux kernel-land using /proc filesystem for quick’n’dirty troubleshooting This blog entry is about modern Linuxes. In other words RHEL6 equivalents with 2.6.3x kernels and not the ancient RHEL5 with 2.6.18 kernel (wtf?!), which is the most common in enterprises unfortunately. And no, I’m not going to use kernel debuggers or SystemTap scripts here, just plain old “cat /proc/PID/xyz” c
A lot of people have asked me whether there’s some sort of index or “table of contents” of my TPT scripts (there’s over 1000 in my TPT script repo right now). I have planned to create such index for years, but never got to it. I probably never will :) So a good way to extract the descriptions of some scripts is to just grep for Purpose: in the scripts directory: grep -i Purpose: ash/*.sql awr/*.sq
Advanced Oracle Troubleshooting Guide – Part 10: Index unique scan doing multiblock reads?! When you troubleshoot an Oracle (performance) problem you usually want to find out what are the problem sessions doing (wrong) and then why are they doing it. The “what” question is usually answered using some wait interface based method – like ASH or SQL*Trace, which both add plenty of extra details to the
このページを最初にブックマークしてみませんか?
『Tanel Poder Consulting』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く