[G4ME]

I looked over that memory tweak thing in the other forum and it left my head spinning, does anyone have step by step instuctions inorder to get my system running up to par. BTW I am unix ilitterate so be kind with terms.

I am willing to donate half a day each day to ubero if I can get some substantial results with my dual G4 500.

[Grozni Majmun]

You could try the Beta of the Macnn configuration client. That would set it all up nicely for you. You can find it here

alternatively, since you already have it installed, you could just, in the terminal, type:

cd /Applications/Ubero
(or whatever folder you keep the Ubero application in)
nohup java -server -cp Agent.jar ubero.agent.Agent -text >/dev/null &

This will start the ubero application but there will be not screen output. You can use the 'top' command to see that it is running (it will just show up as 'java'). You would need to do this twice and each time substitute the name of your ubero client. (I remember from a recent post that you have set it up with two clients, one per processor, right?). This version has 'nohup' which means it will keep running when you log out. It runs faster when you are logged out. The '-server' bit is one version of the famous memory tweak. You may or may not be able to tweak it to a better setting, depending on the amount of RAM you have, but this version is definitely faster than the GUI version, and it is easy.

I hope that helps. I am new to all of this myself and I have just tried to summarize what I have learned from reading older posts over the last few days. Just ask again if you need to.

Happy Crunching

[ 03-01-2002: Message edited by: Grozni Majmun ]

[Shaktai]

Actually the newest verstion is located below. I just tried it today, and it really makes a difference. As one newbie to another, note that when you go through the entire process and then hit config and start, it may seem as though nothing happens. It was pointed out to me though to check the process monitor and sure enough, Java was running full bore in the background crunching assignments, even though I couldn't see anything happening. Just for my own peace of mind I launched the CPU monitor just so I could monitor that something was going on. It also let me see the one time that the client "froze" so that I could restart it. I just use the client then to start and stop as needed. No CLI needed. Very neat. There are some really talented folks on this team.


Clicke to download configuration Client MDC3 beta 6

[ 03-01-2002: Message edited by: Shaktai ]