Slashdot Mirror

← Back to Stories (view on slashdot.org)

Performance Inspector Open Source Project

Posted by michael on from the tool-time dept.

An anonymous reader writes "Performance Inspector puts your finger on the pulse of your C/C++ and Java code, helping you nail down performance bottlenecks and problems with Linux kernel interaction. The suite of tools includes sample-based profiling, monitoring at the thread level, and more."

19 comments

  1. Mac OS X performance tools by norwoodites · · Score: 4, Informative

    If you want to use performance tools like the Performance Inspector on Mac OS X, get the CHUD tools from http://developer.apple.com/tools/performance/. They provide a GUI so you do not need to use the command line expect for amber, the instruction tracer.
    Shikari is a profiler that can use the CPU PMC(performance monitor counters), it can show you where your hot spot is in asm but gives line information if you compiled with -g.

    1. Re:Mac OS X performance tools by dthable · · Score: 1

      That is very cool....do you know of any tools for Windows?

    2. Re:Mac OS X performance tools by Anonymous Coward · · Score: 1, Funny
      Right Click on my computer, and you can set the performance level.


      If you want really good performance, use regedit to set the performance to go up to 11.

    3. Re:Mac OS X performance tools by norwoodites · · Score: 2, Informative

      It is called VTune by Inte.

    4. Re:Mac OS X performance tools by norwoodites · · Score: 1

      That should have been Intel.

  2. Peformance tools on Java... by elphkotm · · Score: 3, Funny

    === RUNNING PERFORMANCE PROFILER ON JAVA APP ===
    ! Performance Tip: Please use C++, instead of Java. This should lead to a noticeable performance increase.
    Launching "java" process...

    --

    <Amanda`> I just went out to the parking lot in my bathrobe to exchange warez CDs.
  3. weed wednesday! by Anonymous Coward · · Score: -1, Offtopic

    It's weed wednesday! Let's go smoke a bowl!

    1. Re:weed wednesday! by Anonymous Coward · · Score: -1, Offtopic

      You shouldn't do drugs, because if you use drugs, you're an open source linux zealot hippie, and open source linux zealot hippies suck.

  4. Don't use those tools! by Anonymous Coward · · Score: -1, Troll

    They're not open source, so please don't use them. There are lots of good open source performance tools available. Please use them instead.

    1. Re:Don't use those tools! by grundy · · Score: 5, Informative

      >They're not open source,
      >so please don't use them.

      What planet are you from nerd-boy?

      From the COPYING file:

      Performance Inspector Components

      Component license
      post GPL
      a2n GPL
      perfutil GPL
      swtrace GPL
      rtdriver GPL
      ptt GPL

      jprof LGPL

    2. Re:Don't use those tools! by Anonymous Coward · · Score: -1, Troll

      They're GPL, but they're not official GNU Free software. If you value Freedom, only use GNU software.

    3. Re:Don't use those tools! by Ed_Moyse · · Score: 2, Interesting
      I don't necessarily think that you ARE a troll, but you certainly aren't very bright. There is plenty of free software that isn't made by GNU. Furthermore, any software released under the GPL is released under identical terms to GNU software.


      In simple language - this is as free as gcc.

  5. Good job by rumpledstiltskin · · Score: 1
    The majority of this project is GPL code with the exception of some LGPL shared libraries
    Kudos to IBM for furthering the use of OSS. This is the kind of support necessary to help bring OSS into the main stream.
  6. SCO Soure Code? by Atomizer · · Score: 2, Funny

    I think this is really just a bunch of SCO utilities that IBM just copied and released. ;)

  7. That's not what the GNU people say. by Anonymous Coward · · Score: 0

    So why are you making such a big deal out of it?

  8. *BSD is dying by Anonymous Coward · · Score: -1, Offtopic
    It is official; Netcraft now confirms: *BSD is dying

    One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.

    FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dying

  9. kernel level profiling? by wdebruij · · Score: 2, Interesting

    from the website:

    "We believe the Linux community will be best served by consolidating most of the performance projects into one or two projects, and then move that functionality into the kernel."

    in the kernel? why oh why would we want profiling tools embedded in the kernel?

    1. Re:kernel level profiling? by grundy · · Score: 1
      Well, in 2.5 we already have it built in. It's called oprofile. There are two places you can do accurate profiling, in hardware, or in the kernel. Some hardware has external interfaces that allows you to do profiling.

      But in this case oprofile or pi have to have a kernel element, so that they have access to the memory map of a program, and can set/read preformance counters in the cpu (or in cpus without perf regs, use a timer pop to sample the running application). And that's the key really when you compare something like this to gprof etc. You are profiling code without having to modify the code.

  10. OpenSource alternative to Intel's VTune? by lfslinux · · Score: 1

    Interesting piece of software. I wonder if "Performance Inspector" was inspired by Intel's VTune Performance Analyzer software ( http://www.intel.com/software/products/vtune/).

    Either way, this might become a popular piece of software, especially if the capabilities and features are somewhat similar to that of the VTune program. Would probably make a good comparison article for DevChannel.org

    --
    Gerard Beekmans