Friday Dec 19, 2014

Three New Dev Tips for C++ Developers

How to Find Out What Resources Your Application Has Used

by Darry Gove

If you want to know how much CPU, memory, or other resources your application has used, you can pre-load a library and define a .fini method that prints out the results. You can also take advantage of the getusage call, which provides some information about CPU time and processes. But more information is available. Darryl provides examples of how to use these two components plus others that fill in the details.

How To Rapidly Identify Performance Opportunities

by Darry Gove

Profiling is critical to improving application performance. Without profiling, it is very easy to guess where the application is spending cycles, and then expend effort optimizing code that has little effect on overall performance. Oracle Solaris Studio 12.4 provides an overview screen designed to focus you on the metrics with the most promise. Darryl Gove walks you through the overview screen and explains what it indicates about your application.

Dev Tip: How to Get Finer Grained Control of Debugging Information

by Ivan Soleimanipour

The new options in Oracle Solaris Studio 12.4 provide much finer-grained control over debug information, which allows you to choose how much information is provided and reduce the amount of disk space needed for the executable. Ivan enumerates the options and provides examples of how to use them.

About the Photograph

I took the picture of the 01 Ducati 748S this summer, in Colorado. It currently has about 1300 miles on the odometer.

- Rick

Follow Rick on:
Personal Blog | Personal Twitter | Oracle Community Profile
  Follow OTN Garage on:
Blog | Community Discussions | Web | Facebook | Twitter | YouTube

Wednesday Jul 31, 2013

Using Ksplice for diagnostic purposes

laptop and stethoscope by jfcherry, on Flickr
laptop and stethoscope by jfcherry (CC BY-SA 2.0)

We've been emphasizing the benefits of using Oracle Linux with Ksplice rebootless updates several times already. The ability to minimize downtime when applying rebootless patches to the Linux Kernel is a feature unique to Oracle Linux, and a growing number of customers realize the benefits of this technology.

Since we acquired Ksplice two years ago, we've continued to improve and further integrate this functionality in Oracle Linux. For example, we implemented the the Ksplice offline client (which I mentioned in this YouTube whiteboard session some time ago), the Ksplice Inspector, or the RedPatch utility.

But did you know that we use Ksplice for diagnostic purposes, too? As part of our Oracle Linux Premier Support offering, we can make use Ksplice to enable additional debugging functionality on your production system, if we need to track down an issue in your environment. Instead of asking you to reboot into a custom Linux kernel that contains additional debugging code, we now simply create a custom Ksplice patch that helps us to gather the required information, while your system keeps running. Once we've obtained the necessary details, you can simply remove the debug patch with Ksplice at runtime again, without any interruption. The additional debugging information helps our support team to determine the root cause of your issue. In case it turns out to be a genuine bug in the Linux kernel, we will then develop and provide a bug fix for this particular problem in the form of a new Ksplice patch, which you can apply while the system keeps humming along. Bug analyzed and fixed, no reboot was required!

To learn more about his feature and the other advantages of Ksplice, take a look at Wim's recent blog post "The Ksplice differentiator".

About

Contributors:
Rick Ramsey
Kemer Thomson
and members of the OTN community

Search

Archives
« April 2015
SunMonTueWedThuFriSat
   
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
  
       
Today
Blogs We Like