|Feedback on my TPTP profiling experiences [message #129151]
||Fri, 25 April 2008 15:16
Originally posted by: mike.bleazard.org|
I think I've had my fill of trying to profile using TPTP. I've found it
a very frustrating experience. It was taken me just shy of 3 full days
to get a small amount of useful information out of it. The effort
involved was just not worth the return.
I'm very surprised that a system that is at release 4.4.1 is so
difficult to use and so unreliable. Why?
The final straw for me was that when trying to profile my application
turned Eclipse into a CPU hog. I've just had 3 attempts at trying to
memory profile my application. Despite the fact that I setup some
sensible filters, I still found myself sitting around for 30 minutes per
go wondering whether some profiling was being done or whether it was
just chasing its own tail.
Enough is enough. I would only tell people to try it if:
a. They had no other option.
b. They have a lot of spare time and a huge amount of patience.
There seems to be a heavy irony that a system that is supposed to help
improve the quality and performance of software is so lacking in both
quality and performance.
Admittedly I've only tried using the profiling part of the system.
How closely do my experiences match with other peoples? Do most people
give up on it very quickly - or have some brave souls persevered?
|Re: Feedback on my TPTP profiling experiences [message #129203 is a reply to message #129151]
||Mon, 28 April 2008 03:31
Originally posted by: n.sherlock.gmail.com|
Mike Bleazard wrote:
> Dear all,
> I think I've had my fill of trying to profile using TPTP. I've found it
> a very frustrating experience. It was taken me just shy of 3 full days
> to get a small amount of useful information out of it. The effort
> involved was just not worth the return.
I had a similar experience. The version that I was using was nearly
impossible to get working, and I fought with it for weeks. A bug fix in
the latest release solved the problem, however, and now it installs
It seems like the system is just not capable of logging much data. Toy
test programs profile fine, but as soon as I try to profile anything CPU
intensive (A ray tracer, for instance), it runs incredibly slow and then
Powered by FUDForum
. Page generated in 0.05783 seconds