* How to get more speed in Ubero *
Simple:

If you like to leave it on the application window pane where it shows it doing work with the blue update bar, Don't! The aquq update bar is stealing a significant amount of power away from the CPU belive it or not (this kind of bar just being onscreen in the background with Ubero in the stopped position can even cause Quicktime to drop several frames per second on a g3).

To avoid the "Aqua tax" simply leave Ubero showing the Statistics pane instead or keep it minimized into the dock. Shrinking the window or putting the Aqua bar off the bottom of the page doesn't work, but when the Finder minimizes to the Dock, it knows not to bother updating the status bar visually and you get that bit of speed back. I've noticed a >5% jump in production with the client since I started always leaving it on the statistics page (which only gets one update per 2 hours instead of several per minute for the text and dozens per second for the pretty aqua status bar).

[Arkham_c]

A batter solution is to run it in command-line mode. You can do this either with the shell scripts posted here, or with the MDC3 beta software, which will configure and start ubero for you in CLI mode.

Thanks for the additional hint. I don't think it would run any faster in the shell than it would minimized to the Dock. Anyone care to do hard numbers analysis on that?

I would like to add however that my tests show the first optimization (and the best) is to run the client on a Mac. I have run a client on up to three PCs (all at 400 MHz), and they can barely keep up together in total with just one g3 iMac at 400 MHz.. funny huh? I can't help but wonder how much faster the work could get done if the client was done in C++ or Cocoa instead of dumpy old Java.

[Shaktai]

Originally posted by <Xapplimatic>:
<STRONG>Thanks for the additional hint. I don't think it would run any faster in the shell than it would minimized to the Dock. Anyone care to do hard numbers analysis on that? </STRONG>

From my experience using both, I did see about an 8-10% increase in the CLI using the memory tweak and the MDC3 beta client installer. Your mileage may vary.

[doggkruse]

Dumpy old java... its funny you say that because the client would probably not be on the mac without java. The Ubero people don't even own a mac for testing....
Geoff

[wheeles]

Originally posted by &lt;Xapplimatic&gt;:
<STRONG>I would like to add however that my tests show the first optimization (and the best) is to run the client on a Mac.
</STRONG>

I read yesterday that Sun were looking at incorporating a number of Apple Java VM tweaks into their Java VMs. Apparently Apple did a good job with their Java implementation. This might go some way to explaining the Mac's superior Java performance (other than merely 'because Macs are better' ).

[SkiBikeSki]

Originally posted by wheeles:
<STRONG>

I read yesterday that Sun were looking at incorporating a number of Apple Java VM tweaks into their Java VMs. Apparently Apple did a good job with their Java implementation. This might go some way to explaining the Mac's superior Java performance (other than merely 'because Macs are better' ).</STRONG>

This might also mean that we will eventually lose our lead over the pentiums.