Re: Profiling options

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Thu Sep 07 2006 - 09:15:18 EDT

  • Next message: Ulrich Köster: "Re: Profiling options"

    I have to take a look at the jprofiler stuff to answer the question.

    Uli
    Am 07.09.2006 um 14:40 schrieb Anjo Krank:

    > Isn't this just an issue if which string to prefix the JVM args
    > with? Couldn't this simply be a prefs setting?
    >
    > Cheers, Anjo
    >
    > Am 07.09.2006 um 14:13 schrieb Ulrich Köster:
    >
    >>
    >> Am 07.09.2006 um 14:04 schrieb Anders Peterson:
    >>
    >>> It would be great if WOLips had a profiling feature/plugin that
    >>> only requires that you have a (any) general java profiler
    >>> installed and integrated with eclipse.
    >>
    >> True, true. Currently you have to do it for each profiler.
    >>
    >> Uli
    >>
    >>>
    >>> I can help test if it works with jprofiler ;-) and I can offer to
    >>> write some documentation for it on the wiki.
    >>>
    >>> /Anders
    >>>
    >>> Ulrich Köster wrote:
    >>>> Let me know if you need help with it.
    >>>> Uli
    >>>> Am 07.09.2006 um 13:35 schrieb Mike Schrag:
    >>>>> Right now there's no way to do it that I'm aware of. The best
    >>>>> option at the moment is to build a deployed version of your app
    >>>>> and use JProfiler on that.
    >>>>>
    >>>>> However, JProfiler has given me access to the source code of
    >>>>> their eclipse plugin to add this support, but I just have not
    >>>>> had time to get around to it.
    >>>>>
    >>>>> m
    >>>>>
    >>>>> On Sep 7, 2006, at 6:45 AM, Anders Peterson wrote:
    >>>>>
    >>>>>> Hi,
    >>>>>>
    >>>>>> I need to memory profile one of my WO applications.
    >>>>>>
    >>>>>> WOLips currently has two options - jmechanic (that is old and
    >>>>>> I never got to work) and tptp (that doesn't seem to work on Mac).
    >>>>>>
    >>>>>> I have jprofiler installed. It comes with an eclipse
    >>>>>> integration plugin, but I was unable to launch my apps from
    >>>>>> within eclipse because I didn't know how to set up the launch
    >>>>>> configurations.
    >>>>>>
    >>>>>> Some time ago I tried a number of different profilers. Several
    >>>>>> of them had eclipse integration plugins, and these looked very
    >>>>>> similar (eclipse GUI). There must be some standard they were
    >>>>>> plugging in to. I didn't have to install (part of) tptp or
    >>>>>> anything, but still there seemed to a standard.
    >>>>>>
    >>>>>> Today I wanted to try the WOLips tptp stuff. After I installed
    >>>>>> it the jprofiler plugin complained about other profiling
    >>>>>> plugins. ?! I was now able to create launch configurations to
    >>>>>> WO apps, but when I launched jprofiler started - which is kind
    >>>>>> of what I wanted.
    >>>>>>
    >>>>>> Is it possible to create a profiled WO launch configuration
    >>>>>> template that allows us to use any profiler (given that they
    >>>>>> are following some standard) and does not force anyone to
    >>>>>> install TPTP, BRIT and a lot of other stuff.
    >>>>>>
    >>>>>> It seems to me that what exists now is actually very close to
    >>>>>> this.
    >>>>>>
    >>>>>> BTW: Jprofiler offer free licenses to open source projects,
    >>>>>> and comes with WO integration as well as eclipse integration
    >>>>>> (but not WOLips integration). ...and it runs on any platform.
    >>>>>>
    >>>>>> /Anders
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>> --http://ojalgo.org/
    >>>>>>
    >>>>>> Mathematics, Linear Algebra and Optimisation with Java
    >>>>>
    >>>
    >>>
    >>> --
    >>> http://ojalgo.org/
    >>>
    >>> Mathematics, Linear Algebra and Optimisation with Java
    >>
    >



    This archive was generated by hypermail 2.0.0 : Thu Sep 07 2006 - 09:15:32 EDT