optimizeit: how to workaround/minimize wrong cput time in Object.wait()
From: NOBODY (antispam_at_0.0.0.0)
Date: 11/05/04
- Previous message: Bjorn Abelli: "Re: Starting UML"
- Next in thread: Robert Klemme: "Re: optimizeit: how to workaround/minimize wrong cput time in Object.wait()"
- Reply: Robert Klemme: "Re: optimizeit: how to workaround/minimize wrong cput time in Object.wait()"
- Reply: Vladimir Kondratyev: "Re: optimizeit: how to workaround/minimize wrong cput time in Object.wait()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 05 Nov 2004 02:48:26 GMT
Hi,
Optimizeit reports imprecise cpu time in Object.wait()
even though you use
record only cpu usage. (also stream read,
Thread.sleep, etc...)
(partially explained in
http://groups.google.com/groups?q=optimizeit+Thread.sleep+Object.wait&hl=en&lr=&safe=off&selm=41008621%241%40newsgroups.borland.com&rnum=1
)
????? Is there anyways to work it around or minimize that effect?
Whether I use sampling or instrumentation mode, it is
very off by large fraction of thread time share%.
Changing sampling interval didn't help either.
I'm stuck! Feel like this 800$ piece of software is useless!
(optimizeit profile 4.2 enterprise edition, build 020502,
in case you know anything about that version)
Thanks.
- Previous message: Bjorn Abelli: "Re: Starting UML"
- Next in thread: Robert Klemme: "Re: optimizeit: how to workaround/minimize wrong cput time in Object.wait()"
- Reply: Robert Klemme: "Re: optimizeit: how to workaround/minimize wrong cput time in Object.wait()"
- Reply: Vladimir Kondratyev: "Re: optimizeit: how to workaround/minimize wrong cput time in Object.wait()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|