Joseph Dane wrote:
>as far as filing bug reports go, I certainly have no moral objections
>(?) to filing these, but I typically have nothing to file. eclipse is
>slower than I'd like: is that a bug?
If you think it is, then it is.
Before you file a bug-report, though, you can narrow down the possibilities
for what it might be.. At this point, eliminating possibilities is an
excellent start.
My first approach is always the Yogi Berra Principle:
You can see a lot just by observing.
Start with Activity Monitor.app, found in /Applications/Utilities. It's
how I found the cause of the supposed Java I/O slowdowns lay in swapping,
which caused I/O contention in a program intended to measure I/O speed. I
suggest reading my full explanation:
<http://lists.apple.com/archives/java-dev/2005/Aug/msg00053.html>
I spent a lot more time just observing, taking notes, and trying different
settings than I ever spent writing the successful test-case, compiling,
etc. Writing up the explanation took some time, too, but unless you find
something definitive, all you'll be doing at this point is eliminating
possibilities, which needs no written explanation.
Once you've eliminated possibilities, whatever remains may need closer
observation, and that may mean different tools. Or not. Depending on the
results. At that point, though, you will have some real results, based on
real systematic observation, and that's better than any amount of random
speculation.
Understanding is the only gateway to effective action.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
