Forum Stats

  • 3,733,142 Users
  • 2,246,704 Discussions
  • 7,856,531 Comments

Discussions

whatis 'limited feature mode' in discover?

Hi,

I was playing with discover from Studio 12 update 4, and found the performance of instrumented binaries really slow (factor of 50 - 60 slower than uninstrumented binaries). With -l, the performance is far better, but I wonder what these 'limited features' really mean. The documentation does not expand on this. Could someone explain the tradeoff between 'normal instrumentation' and 'limited feature mode' (i.e. which checks are done/omitted in these modes)?

Regards

Dieter Ruppert

Best Answer

  • Darryl Gove-Oracle
    Darryl Gove-Oracle Member Posts: 82
    edited February 2015 Accepted Answer

    Full instrumentation means taking the binaries apart and checking (nearly) every memory operation to see if it's valid or not. So the slowdown is proportional to the number of memory operations, so some apps will be impacted more than others. With light instrumentation the tool is just checking the library calls, and not instrumenting the binary. So you can pick up some things - like memory that wasn't freed, or double free - but you cannot get anywhere near the level of detail from as from full instrumentation. You might find this blog post from Raj interesting: https://blogs.oracle.com/raj/entry/move_over_purify_and_valgrind He talks about the slowdown from instrumentation. Regards, Darryl.

Answers

  • Darryl Gove-Oracle
    Darryl Gove-Oracle Member Posts: 82
    edited February 2015 Accepted Answer

    Full instrumentation means taking the binaries apart and checking (nearly) every memory operation to see if it's valid or not. So the slowdown is proportional to the number of memory operations, so some apps will be impacted more than others. With light instrumentation the tool is just checking the library calls, and not instrumenting the binary. So you can pick up some things - like memory that wasn't freed, or double free - but you cannot get anywhere near the level of detail from as from full instrumentation. You might find this blog post from Raj interesting: https://blogs.oracle.com/raj/entry/move_over_purify_and_valgrind He talks about the slowdown from instrumentation. Regards, Darryl.

  • user13104769
    user13104769 Member Posts: 11
    edited February 2015

    Hi,

    thanks for the clarification. As I understand it, this 'limited feature mode' misses most of the error categories listed in the manual, in particular UMRs and ABRs. I will play with optimization, perhaps this might reduce the frequency of memory references and bring the performance impact to a more tolerable level.

    Regards

    Dieter Ruppert

  • Darryl Gove-Oracle
    Darryl Gove-Oracle Member Posts: 82
    edited February 2015

    If you are interested in near realtime memory error detection, then you might take a look at the ADI feature on SPARC M7. You can sign up for access here: https://swisdev.oracle.com/ And there's information on ADI here: https://swisdev.oracle.com/_files/What-Is-ADI.html Darryl.

This discussion has been closed.