and also thanks to Stefan. It turned out we did not need to analyze the trace as detailed after all.
Well, it was quite nice to do something outside my usual borders. I am a software guy and OS is not usually my playground.
Von : ***@gmail.com
Datum : 09/10/2018 - 01:30 (GMT)
An : ***@soocs.de
Cc : firstname.lastname@example.org, ***@bluewin.ch
Betreff : Re: Stack trace interpretation
I've just spent the day playing with stack traces.
Stefan, your paper and presentation are outstanding!
Of particular interest was the wait_even["event name"] syntax that allows dumping stack traces in a 10046 trace file.
Somehow I had missed learning about that, very cool.
Should anyone be interested in this topic, here is my reading list for the day.
Note: of course there is Perl :)
Journey to the Stack, Part I
Anatomy of a Program in Memory
How The Kernel Manages Your Memory
If you are interested in dumping the values from little endian words
Perl pack tutor
Leading up to:
Identifying performance issues beyond the Oracle wait interface
Troubleshooting Oracle performance issues beyond the Oracle wait interface
Certifiable Oracle DBA and Part Time Perl Evangelist
Principal Consultant at Pythian
Pythian Blog http://www.pythian.com/blog/author/still/
On Wed, Aug 1, 2018 at 6:08 AM Stefan Koehler <***@soocs.de> wrote:
the numbers are described on slide 10 (http://www.soocs.de/public/talk/160616_DOAG_Regio_NUE_Identifying_Performance_Issues_Beyond_The_Oracle_Wait_Interface_PPT.pdf) or on page 5 (http://www.soocs.de/public/talk/151118_DOAG2015_Identifying_Performance_Issues_Beyond_The_Oracle_Wait_Interface_PDF.pdf).
Independent Oracle performance consultant and researcher
Post by email@example.com
I like to know what the numbers marked in red mean.I guess it is something like wait time in milliseconds.
I am also wondering about the moduls called.
E.g. gipcWaitF. My guess is that g somewhat stands for cluster and ipc might refer to network communication. These are waits related to the ocssd.