Mac Pro 2 Quad Xeon Processors 8 cores total big adv

[mrfrankmrfrank]

I have a friend who I am trying to get into folding@home. He spent something like 4 grand on a mac pro with two quad core processors for a total of 8 cores. My friend has a lot of cash but not a lot of computer smarts. Today I threw the mac folding@home client on there, (not the console version) just to get it folding for now. I noticed that it was only folding on roughly 20% of his total cpu power. His first core that downloaded was an a1 core so I know that has it's limitations on how many cores it can utilize. I'd be very interested in getting him some big adv units.

From what I've read, this will require running a linux version of folding@home. I have personally been using notfred's vm for quite some time so I would know how to install that, but vm player is not available for mac. I could easily install windows in his boot camp, but he'll never stay in windows.

If I have any chance of getting him some big adv units, it will have to be successfully done while he is still booted in osx. I know vm player isn't avail for mac os, but I did find this http://www.virtualbox.org/wiki/VirtualBox

I wonder if anyone knows if this virtual box can run notfred's, and if it can, would virtual box support 8 cores.

If that is not a viable option, is the only other option perhaps installing a full linux vm like ubuntu using perhaps vmware or something like that.

Any direction would be great guys! Thanks,
Ryan

[thideras]

Your post got caught up in our spam filter, I removed it for you. :)

You should have a knowledgeable folding team member to answer your questions shortly, so sit tight.

[mrfrankmrfrank]

thanks, good looking out.

p.s. from what I read about the bigadv units is that you only get them using some linux client. Is it possible that the mac os smp client can download bigadv units?

[dark bishop]

I think bigadv are purely linux units. I'm fairly sure you can run smp2 and get A3 work units though and with a quad xeon you should easily get the bonus points for them.

[Bluefalcon13]

as far as I know, the mac client supports -bigadv you may want to look a little further into it

as far as easy way to fold NORMAL smp units on osx, setup the command line install version of F@H, then download a wonderful gui call InCrease. It has tons of options, including run at startup, and auto-pause on battery (the battery thing is strangly absent from the OSX -configonly menus....)

[mrfrankmrfrank]

The reason why I got confused as to whether or not the mac client supported big adv units is because from what I had read on my sites, the linux client was the only client to support bigadv, but then I saw one remark from a user perhaps on this forum in another thread that had mentioned getting bigadv on a linux or unix (mac) system I believe was the quote.

I'll continue to do my research, but perhaps an expert or someone more knowledgeable will read this thread and chime in.

Thanks guys for any further help!

[mrfrankmrfrank]

p.s. another reason why I was perhaps leaning away from doing the console client on his mac was because, unless I can hide it, he'll be tempted to toy. People can never just seem to leave something alone when they don't know what it is. What is nice about the other mac client is that it runs in the background and he'll never see it.

The only way I was going to consider doing perhaps a vm on his machine was if that was the ONLY way to get bigadv units because from what i've read, the bigadv units are worth it. I don't have an 8 core machine myself (that's my next project) so I haven't seen a bigadv unit first hand. And even then I was going to find a way to run the vm in the background.

even more p.s. He truly does know that his computer is folding@home. Me wanting to hide the client is more or less for his own good. I just wanted to explain that so people didn't think I was trying to put it on his comp without him knowing it. I did the same thing on my father's computer so he wouldn't mess with it. I installed the windows smp client on his dual core and then used a command line program called hstart to start the client in the background upon boot. The only way you know it's running is by looking at the processes.

[Macaholic]

You can easily fold -bigadv units natively in OS X. Consider using InCrease (http://calxalot.net/InCrease/) or Finstall (http://fahwiki.net/index.php/A_Complete_Guide_to_Using_FINSTALL_for_NEWbies) to automate the start-up and shut-down of the console client.

[ChasR]

Mac beat me to it, while I was editing the -bigadv checklist in the stickies to include Intel/OSX.

[mrfrankmrfrank]

haha, I had been reading the sticky on the bidadv and it said you MUST use the linux client, and I always trust the stickies, thus confusion ensued.... haha. Is the mac os CONSOLE client the only client that can fold the bigadv units, or can the installer client do it as well? Are you both suggesting that the console version is generally better?

[Bluefalcon13]

p.s. another reason why I was perhaps leaning away from doing the console client on his mac was because, unless I can hide it, he'll be tempted to toy. People can never just seem to leave something alone when they don't know what it is. What is nice about the other mac client is that it runs in the background and he'll never see it.

The only way I was going to consider doing perhaps a vm on his machine was if that was the ONLY way to get bigadv units because from what i've read, the bigadv units are worth it. I don't have an 8 core machine myself (that's my next project) so I haven't seen a bigadv unit first hand. And even then I was going to find a way to run the vm in the background.

even more p.s. He truly does know that his computer is folding@home. Me wanting to hide the client is more or less for his own good. I just wanted to explain that so people didn't think I was trying to put it on his comp without him knowing it. I did the same thing on my father's computer so he wouldn't mess with it. I installed the windows smp client on his dual core and then used a command line program called hstart to start the client in the background upon boot. The only way you know it's running is by looking at the processes.

increase runs in the dock, and is just like your standard app. its very easy to leave it on the dock, and ignore it :)

Additionally, InCrease allows you to setup the client to run on boot, but I think it will still open a window. With OSX, hitting the red circle doesnt actually close a program, only the window that is open... easy solution, just have em hit the red circle with the X in it, but not do Applekey-Q (cause that fully quits the app).

[Bluefalcon13]

haha, I had been reading the sticky on the bidadv and it said you MUST use the linux client, and I always trust the stickies, thus confusion ensued.... haha. Is the mac os CONSOLE client the only client that can fold the bigadv units, or can the installer client do it as well? Are you both suggesting that the console version is generally better?

Please remember, OSX is just a 'special' flavor of BSD. Most of the same tools that work in FreeBSD can easily be used in OSX, although some modifications may be needed. Please remember, while there is a decent OS-X crowd here on OCForums, it is by no means the majority here. Windows/Linux users are definitely the main demographic of this forums :)

Most of the stickies are geared towards newbie folders running windows or linux. I have personally stopped folding on my MacBook Pro, but I folded for about 2-3 months with it. Use increase, it even allows you to set additional flags. http://www.teammacosx.com/software.html is a great place to download InCrease, and there are a few guides for setting up F@H on a mac there as well. Just make sure you put 32 in the team block :D

I am still unsure if increase will allow you to do -bigadv units, but, that would be a question better sent to Macoholic. The way I always installed the OS-X folding client was fairly simple. Open finder, goto applications, find Folding@Home, right click, show contents, copy everything, and put it in its own folder, where ever youd like. Then all you have to do is point increase to it so you can monitor/start the client whenever youd like. Granted thats a bit of a simplification, but the general process for getting -bigadv units (post install of client) should be exactly the same on OS-X (flags, passkey, etc).

[mrfrankmrfrank]

From what I read about the mac osx smp installer is that there is no need to add additional flags such as -bigadv because it is already configured in the client. I read this I believe off of the stanford site. Under system preferences, there is the folding@home configuration which has an additional client parameters box where i entered -smp 8.

I understand why you guys are urging me to use the console version, I much prefer it myself on my windows machines, but if the osx smp installer can do the bigadv units, that will just be easier given the situation on this guy's computer. If anyone knows if the smp installer can do the bigadv, that would be great, otherwise if anyone can help me figure out how to use increase to configure the mac console client to get the bigadv units, that would be great too, but only if it is deemed the only option on a mac os..

[Macaholic]

I am still unsure if increase will allow you to do -bigadv units, but, that would be a question better sent to Macoholic.

Simply enter the -bigadv flag under "Additional args" (http://calxalot.net/InCrease/Help/screenshots.html) and check the box. Quite easy. :)

[Macaholic]

From what I read about the mac osx smp installer is that there is no need to add additional flags such as -bigadv because it is already configured in the client.

You still have to enter flag arguments regardless of which you use. The problem with the installer version is that it DOES NOT contain the 6.29 client binary so you will have to drop in the new binary in order to keep from getting saddled with older, smaller A1 and A2 units.

[mrfrankmrfrank]

ahhh macaholic!! when they mentioned macaholic I thought they were referring to a forum or a group of some kind. I didn't realize they were talking about a folder! haha.

So what you're saying macaholic is that the mac osx smp installer isn't updated enough to get the a3 units. So I should download the console client and configure it with increase adding the -bigadv flag?

[Macaholic]

So what you're saying macaholic is that the mac osx smp installer isn't updated enough to get the a3 units. So I should download the console client and configure it with increase adding the -bigadv flag?

Indeed, that is what I'm saying. The console client is my friend, and it can be yours too. ;)

[mrfrankmrfrank]

should we hug it out?

[Macaholic]

should we hug it out?

Not until we're invited to appear on Oprah. Then we can. :grouphug:

[mrfrankmrfrank]

haha, the next time I go over to my friend's house, I'll have to do the following.

His username is new and this is the first time he is folding, so I will have to create a passkey for his name.

Then I will configure the mac osx console client and set it up with increase and the following flags -smp 8 -verbosity 9 while holding off on adding the -bigadv flag until he has completed 10 a2 / a3 core's using his passkey, then once he has completed the 10 or so units, add the -bigadv flag.

Correct me if I messed anything up on that plan, I was basing this off of the -bigadv checklist sticky.

After he has completed 10 a2/a3 work units using a passkey and then I add the -bigadv flag after that in increase, he should hopefully receive the bigadv units correct?

[Bluefalcon13]

From what I read about the mac osx smp installer is that there is no need to add additional flags such as -bigadv because it is already configured in the client. I read this I believe off of the stanford site. Under system preferences, there is the folding@home configuration which has an additional client parameters box where i entered -smp 8.

I understand why you guys are urging me to use the console version, I much prefer it myself on my windows machines, but if the osx smp installer can do the bigadv units, that will just be easier given the situation on this guy's computer. If anyone knows if the smp installer can do the bigadv, that would be great, otherwise if anyone can help me figure out how to use increase to configure the mac console client to get the bigadv units, that would be great too, but only if it is deemed the only option on a mac os..

I dont TRUST the OSX installer version. I much prefer InCrease with manual install of client for folding... BTW on my mac, I dont use the CLI, mostly cause I'm lazy, but partially cause InCrease is pretty cool... the fact that adding battery pausing makes me happy with my MacBook Pro...

Ironically I use the CLI all the time for work, but never for folding :P

[mrfrankmrfrank]

macaholic? any input on my plans there?

[Surferseth]

You can use the console or the installer for -bigadv. Just need to replace the fah6 binary in your ~/Library/Folding@home directory with the 6.29r1 (comes with the console version download) and set your parameters (in system prefs or in the console).

Your plan to run 10 A2 or A3 cores with passkey before starting the -bigadv WUs is a good idea :thup:

[Macaholic]

macaholic? any input on my plans there?

Yes. That sounds like a good plan. Once you start running -bigadv units, change -smp 8 to -smp 16;

http://i682.photobucket.com/albums/vv190/iMacaholic/p2681-smp16.png

[Shiggity]

:drool:

:rock:

[mrfrankmrfrank]

haha, you guys are alright. i don't care what [H]ard forum guys say about you. ;) haha, jk.

I'll post here if I run into any problems when I finally get over to his house.

Anyone care to guess what the ppd are gonna be on this machine with bigadv units?

Thanks guys

[mrfrankmrfrank]

p.s. the hard forum thing was just a joke. i don't fold for them or anything.

[torin3]

p.s. the hard forum thing was just a joke. i don't fold for them or anything.

Don't worry about it. I'm pretty sure everybody got that it was a joke. And we're a friendly bunch here.

:grouphug:

[mrfrankmrfrank]

haha, I just wanted to clarify / make sure. I'm new to overclockers forum, and I want to show much respect. I've seen far too many times guys will join a forum and show no respect to the members who post day in and day out. You guys have been helpful and great thus far.

[Bluefalcon13]

p.s. the hard forum thing was just a joke. i don't fold for them or anything.

I HATE YOU!!!!!!!1111!!!!one!!!!!!














Oh, you said it WAS a joke... carry on then... you may stay :P

(sorry... couldnt let it slide for the newbie :D )

[mrfrankmrfrank]

haha, I actually had to scroll up and re-read through some parts of the thread to see if I had accidentally ****ed you off.

It was only after I failed to find such insults that I scrolled down to see the rest of your post.

/noob

[Bluefalcon13]

haha, I actually had to scroll up and re-read through some parts of the thread to see if I had accidentally ****ed you off.

It was only after I failed to find such insults that I scrolled down to see the rest of your post.

/noob



<---- winner, yay for mildly excessive enter key hits :P

I figured the !!!!!!!111!!!!!!one!!!!! was a dead give-away... O.o

[mrfrankmrfrank]

I'm going over to the guy's house tomorrow. I'm gonna try increase and the latest console client. I'm gonna get him set with a passkey and get him folding some a/2 a/3 units. Then some time next week after he's folded at least 10, add the big adv. You'll see me on here tomorrow in a panic if I can't figure something out.

[Mark620]

I think bigadv are purely linux units. I'm fairly sure you can run smp2 and get A3 work units though and with a quad xeon you should easily get the bonus points for them.

I get bonus points on windows xp GRO-A3 P6012(R0,C270, G53) units on a Q6600 using 3 cores...not many tho...

[Mark620]

Another poke at the noob :)

haha, I had been reading the sticky on the bidadv and it said you MUST use the linux client, and I always trust the stickies, thus confusion ensued.... haha.

Just dont come running back because you did not check your spelling..."bidadv" :eek:

[mrfrankmrfrank]

ouch...

[mrfrankmrfrank]

haha

[mrfrankmrfrank]

well we all know the newest cores from stanford. the -bigdaddy units

[Mark620]

sorry...but I just "had to"
lol

PS. welcome to the team.

[mrfrankmrfrank]

well I finally got over to this guys house to try and install the latest 6.29r1 client so that he can start getting the bigadv units after 10 successful a2/a3s. Originally as I had said, I had installed the mac smp installer and did not give him a passkey etc. Everyone here recommended that I use increase to configure the client and set it to start upon boot.

I've heard good things about increase, but quite frankly I was completely shocked when I finally tried to use it and was confused as to what to do. I was under the impression that increase made it easy to install and set up folding@home on a mac. I downloaded and installed increase, and opened it. There it was. sitting, waiting. telling me no folding@home was installed on the machine etc. I looked for a way to install folding@home from increase....didn't see it. Saw the configuration settings, got even more frustrated.

Then I thought, well, I'll just install the console client myself and then maybe increase will do something. So I did, I downloaded and installed the console client myself, it wasn't difficult at all as it was similar to the smp console client on windows except instead of command prompt I was using terminal.

Then, sure enough, increase showed some activity. I configured everything in preparation for the bigadv units and stared. The client went and downloaded a1core for whatever reason. (seems like a waste to me) since it can't fold on all of the computers cores.

Then I realized this would not work. I couldn't leave terminal open on his screen. He'd be interested in closing it every day. I thought perhaps increase would allow me to hide the console or something. Maybe this is a feature I missed.

So knowing that this would not work, I tried plan "b" as suggested in this thread earlier. Download and install the mac installer client, then simply replace the folding@home application files with the 6.29r1 client files. I did this, started folding@home from the system preferences and then checked the log files. According to the fahlog, I am indeed running the 6.29r1 client. I configured the client using the system preferences and set it up with his passkey and the flags -smp 8 -verbosity 9. (waiting to add bigadv until he has completed 10 work units).

What I want to know is as follows. I know that in the sticky about bigadv units, it says to not enable advmethods. This is not an option in the folding@home mac system preferences, so I do not know if I need to disable it or not. (my assumption is that by default it is not enabled) Then furthermore, I want to know why on earth it would again download another a1 core. Downloading another a1 core to work on is literally crippling the potential of that machine. It will only fold 2000 ppd until tomorrow when it finishes that first core on the machines like one core its using before it gets a chance to download another work unit.

Is there something I'm doing, some setting, anything that would only give him an a1 core? Do you guys think his setup will start using multi-core cores soon? Have I configured his machine accordingly to start getting bigadv eventually?

Here is the client cfg file and the fahlog from his /library/folding@home folder.

# Mac OS X SMP Console Edition ################################################
################################################## #############################

Folding@Home Client Version 6.29r1

http://folding.stanford.edu

################################################## #############################
################################################## #############################

Launch directory: /Users/KERN/Library/Folding@home
Executable: /Applications/Folding@home.app/fah6
Arguments: -verbosity 9 -smp 8

[02:32:35] - Ask before connecting: No
[02:32:35] - Machine ID: 1
[02:32:35]
[02:32:35] Work directory not found. Creating...
[02:32:35] Could not open work queue, generating new queue...
[02:32:35] - Preparing to get new work unit...
[02:32:35] - Autosending finished units... [02:32:35]
[02:32:35] Cleaning up work directory
[02:32:35] Trying to send all finished work units
[02:32:35] + No unsent completed units remaining.
[02:32:35] - Autosend completed
[02:32:35] + Attempting to get work packet
[02:32:35] Passkey found
[02:32:35] - Will indicate memory of 6144 MB
[02:32:35] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 5
[02:32:35] - Connecting to assignment server
[02:32:35] Connecting to http://assign.stanford.edu:8080/
[02:32:36] Posted data.
[02:32:36] Initial: 40AB; - Successful: assigned to (171.64.65.63).
[02:32:36] + News From Folding@Home: Welcome to Folding@Home
[02:32:36] Loaded queue successfully.
[02:32:36] Sent data
[02:32:36] Connecting to http://171.64.65.63:8080/
[02:32:37] Posted data.
[02:32:37] Initial: 0000; - Receiving payload (expected size: 608186)
[02:32:40] - Downloaded at ~197 kB/s
[02:32:40] - Averaged speed for that direction ~197 kB/s
[02:32:40] + Received work.
[02:32:40] + Closed connections
[02:32:40]
[02:32:40] + Processing work unit
[02:32:40] Work type a1 not eligible for variable processors
[02:32:40] Core required: FahCore_a1.exe
[02:32:40] Core not found.
[02:32:40] - Core is not present or corrupted.
[02:32:40] - Attempting to download new core...
[02:32:40] + Downloading new core: FahCore_a1.exe
[02:32:40] Downloading core (/~pande/OSX/x86/Core_a1.fah from www.stanford.edu)
[02:32:40] Initial: AFDE; + 10240 bytes downloaded
[02:32:41] Initial: 5539; + 20480 bytes downloaded
[02:32:41] Initial: F3C4; + 30720 bytes downloaded
[02:32:41] Initial: 93EC; + 40960 bytes downloaded
[02:32:41] Initial: A069; + 51200 bytes downloaded
[02:32:41] Initial: 9C9E; + 61440 bytes downloaded
[02:32:41] Initial: 5679; + 71680 bytes downloaded
[02:32:41] Initial: 55EE; + 81920 bytes downloaded
[02:32:41] Initial: CA96; + 92160 bytes downloaded
[02:32:41] Initial: 87C5; + 102400 bytes downloaded
[02:32:42] Initial: 1A84; + 112640 bytes downloaded
[02:32:42] Initial: C268; + 122880 bytes downloaded
[02:32:42] Initial: C621; + 133120 bytes downloaded
[02:32:42] Initial: 3339; + 143360 bytes downloaded
[02:32:42] Initial: F180; + 153600 bytes downloaded
[02:32:42] Initial: 7B84; + 163840 bytes downloaded
[02:32:42] Initial: A19C; + 174080 bytes downloaded
[02:32:42] Initial: 1797; + 184320 bytes downloaded
[02:32:42] Initial: 187B; + 194560 bytes downloaded
[02:32:42] Initial: 9058; + 204800 bytes downloaded
[02:32:42] Initial: E595; + 215040 bytes downloaded
[02:32:42] Initial: EC12; + 225280 bytes downloaded
[02:32:42] Initial: 9DBF; + 235520 bytes downloaded
[02:32:42] Initial: 641A; + 245760 bytes downloaded
[02:32:42] Initial: 59F0; + 256000 bytes downloaded
[02:32:42] Initial: 6B5B; + 266240 bytes downloaded
[02:32:42] Initial: 6FEF; + 276480 bytes downloaded
[02:32:42] Initial: FC9B; + 286720 bytes downloaded
[02:32:42] Initial: AE8B; + 296960 bytes downloaded
[02:32:42] Initial: 4620; + 307200 bytes downloaded
[02:32:42] Initial: 0167; + 317440 bytes downloaded
[02:32:42] Initial: 981A; + 327680 bytes downloaded
[02:32:43] Initial: 47C5; + 337920 bytes downloaded
[02:32:43] Initial: 101E; + 348160 bytes downloaded
[02:32:43] Initial: CF86; + 358400 bytes downloaded
[02:32:43] Initial: 92E6; + 368640 bytes downloaded
[02:32:43] Initial: 64D0; + 378880 bytes downloaded
[02:32:43] Initial: 89D4; + 389120 bytes downloaded
[02:32:43] Initial: 8928; + 399360 bytes downloaded
[02:32:43] Initial: 3AEA; + 409600 bytes downloaded
[02:32:43] Initial: 2222; + 419840 bytes downloaded
[02:32:43] Initial: B8D8; + 430080 bytes downloaded
[02:32:43] Initial: F71F; + 440320 bytes downloaded
[02:32:43] Initial: CBE7; + 450560 bytes downloaded
[02:32:43] Initial: A7DE; + 460800 bytes downloaded
[02:32:43] Initial: 7875; + 471040 bytes downloaded
[02:32:43] Initial: 0564; + 481280 bytes downloaded
[02:32:43] Initial: 7439; + 491520 bytes downloaded
[02:32:43] Initial: 684F; + 501760 bytes downloaded
[02:32:43] Initial: 50A5; + 512000 bytes downloaded
[02:32:43] Initial: 1945; + 522240 bytes downloaded
[02:32:43] Initial: 1D09; + 532480 bytes downloaded
[02:32:43] Initial: 94B4; + 542720 bytes downloaded
[02:32:43] Initial: FD25; + 552960 bytes downloaded
[02:32:43] Initial: 1A20; + 563200 bytes downloaded
[02:32:43] Initial: 5A1C; + 573440 bytes downloaded
[02:32:43] Initial: 0A03; + 583680 bytes downloaded
[02:32:44] Initial: 0D46; + 593920 bytes downloaded
[02:32:44] Initial: E768; + 604160 bytes downloaded
[02:32:44] Initial: 782D; + 614400 bytes downloaded
[02:32:44] Initial: 783C; + 624640 bytes downloaded
[02:32:44] Initial: 109F; + 634880 bytes downloaded
[02:32:44] Initial: 2FFC; + 645120 bytes downloaded
[02:32:44] Initial: 2C97; + 655360 bytes downloaded
[02:32:44] Initial: 22E8; + 665600 bytes downloaded
[02:32:44] Initial: 1233; + 675840 bytes downloaded
[02:32:44] Initial: C309; + 686080 bytes downloaded
[02:32:44] Initial: 51BB; + 696320 bytes downloaded
[02:32:44] Initial: 573B; + 706560 bytes downloaded
[02:32:44] Initial: 60DB; + 716800 bytes downloaded
[02:32:44] Initial: 8903; + 727040 bytes downloaded
[02:32:44] Initial: 337D; + 737280 bytes downloaded
[02:32:44] Initial: 16D9; + 747520 bytes downloaded
[02:32:44] Initial: 3AA7; + 757760 bytes downloaded
[02:32:44] Initial: 5438; + 768000 bytes downloaded
[02:32:44] Initial: 8514; + 778240 bytes downloaded
[02:32:44] Initial: 8338; + 788480 bytes downloaded
[02:32:44] Initial: 1942; + 798720 bytes downloaded
[02:32:44] Initial: 2075; + 808960 bytes downloaded
[02:32:44] Initial: 0840; + 819200 bytes downloaded
[02:32:44] Initial: 8440; + 829440 bytes downloaded
[02:32:45] Initial: 9DFB; + 839680 bytes downloaded
[02:32:45] Initial: 1709; + 849920 bytes downloaded
[02:32:45] Initial: 98C4; + 860160 bytes downloaded
[02:32:45] Initial: 89A9; + 870400 bytes downloaded
[02:32:45] Initial: 4905; + 880640 bytes downloaded
[02:32:45] Initial: F3D6; + 890880 bytes downloaded
[02:32:45] Initial: 2449; + 901120 bytes downloaded
[02:32:45] Initial: 5216; + 911360 bytes downloaded
[02:32:45] Initial: 99A3; + 921600 bytes downloaded
[02:32:45] Initial: 83ED; + 931840 bytes downloaded
[02:32:45] Initial: B599; + 942080 bytes downloaded
[02:32:45] Initial: FB0B; + 952320 bytes downloaded
[02:32:45] Initial: 6073; + 962560 bytes downloaded
[02:32:45] Initial: 2D4B; + 972800 bytes downloaded
[02:32:45] Initial: FDE0; + 983040 bytes downloaded
[02:32:45] Initial: 963D; + 993280 bytes downloaded
[02:32:45] Initial: 86FA; + 1003520 bytes downloaded
[02:32:45] Initial: BA55; + 1013760 bytes downloaded
[02:32:45] Initial: 73EC; + 1018323 bytes downloaded
[02:32:45] Verifying core Core_a1.fah...
[02:32:45] Signature is VALID
[02:32:45]
[02:32:45] Trying to unzip core FahCore_a1.exe
[02:32:45] Decompressed FahCore_a1.exe (3246776 bytes) successfully
[02:32:45] + Core successfully engaged
[02:32:51]
[02:32:51] + Processing work unit
[02:32:51] Work type a1 not eligible for variable processors
[02:32:51] Core required: FahCore_a1.exe
[02:32:51] Core found.
[02:32:51] - Using generic /Applications/Folding@home.app/mpiexec
[02:32:51] Working on queue slot 01 [March 5 02:32:51 UTC]
[02:32:51] + Working ...
[02:32:51] - Calling '/Applications/Folding@home.app/mpiexec -np 4 -host 127.0.0.1 ./FahCore_a1.exe -dir work/ -nice 19 -suffix 01 -checkpoint 5 -verbose -lifeline 3782 -version 629'

[02:32:51]
[02:32:51] *------------------------------*
[02:32:51] Folding@Home Gromacs SMP Core
[02:32:51] Version 1.74 (September 24, 2007)
[02:32:51]
[02:32:51] Preparing to commence simulation
[02:32:51] - Looking at optimizations...
[02:32:51] - Created dyn
[02:32:51] - Files status OK
[02:32:51] this execution.
[02:32:51] - Previous termination of core was improper.
[02:32:51] - Going to use standard loops.
[02:32:51] - Files status OK
[02:32:51] - Expanded 607674 -> 3255941 (decompressed 535.8 percent)
[02:32:51] - Starting from initial work packet
[02:32:51]
[02:32:51] Project: 3064 (Run 0, Clone 452, Gen 20)
[02:32:51]
[02:32:51] Entering M.D.
[02:32:57] checkpoint
[02:32:57] ilename:
[02:32:57] Protein: p3064_lambda5_2003
[02:32:57] Writing local files
[02:32:58] boost OK.
[02:32:58] Writing local files
[02:32:58] Completed 0 out of 5000000 steps (0 percent)
[02:37:57] Timered checkpoint triggered.
[02:42:57] Timered checkpoint triggered.
[02:43:42] Writing local files
[02:43:42] Completed 50000 out of 5000000 steps (1 percent)
[02:48:42] Timered checkpoint triggered.
[02:53:42] Timered checkpoint triggered.
[02:54:33] Writing local files
[02:54:33] Completed 100000 out of 5000000 steps (2 percent)


and

[settings]
username=
team=
passkey=***
extra_parms=-verbosity 9 -smp 8
machine_id=1
bigpackets=big
machineid=1

[http]
active=no
host=
port=
user=
pass=

[core]
checkpoint=5
addr=

[Mark620]

You need to change team=32 All other settings for that parameter are incorrect.

Right now it seems Stanford needs A1's folded.
They are not about maximizing our points.
They are about the science.

[ChasR]

Doesn't look to be configured correctly, unless you deleted user name and team number from the client.cfg.
If you add -advmethods, at least you have a chance of getting an a3 WU.

p3064's a quad only WU with a short deadline.

Doesn't that machine have HT? If so and it's on in bios, you should be using -smp 16.

[mrfrankmrfrank]

I had deleted the username and team id from the post. Those settings are fine in that regard.

It does have hyperthreading, and I should have set it to smp 16, I just forgot to.

I was under the impression that you should not have -advmethods if you want to eventually get the bigadv.

If the reason why he got an a1 core is because that's what they need, then that's fine. I just wanted to make sure it wasn't something I had done to result in him failing to get a multi-core work unit.

[mrfrankmrfrank]

So do you guys think I configured it correctly?

[ChasR]

Problem is that a1 core WUs don't count towards bonus qualification, while a3 WUs do. You've got to reconfigure it anyway to add -bigadv, so drop -advmethods then.

[mrfrankmrfrank]

When I asked if you guys thought I had configured it correctly, I meant correctly as in the clients ability to receive a2/a3 work units. He needs to get the 10 required a2/a3s under his new passkey before I can change it to -bigadv and potentially start receiving the bonus points.

So in that regard, do you think I've configured the client thus far, correctly enough to receive the a/2's a/3s, because so far he's only received a/1s and I was fearing it was something I had done.... It's upsetting to me to see a 16 core machine only using 20% of it's cpu according to the activity monitor.

[ChasR]

It's tough to know whether to set it up to fold a2 WUs or a3 WUs when the mix assigned by Stanford changes every day. On all my SMP rigs that I monitor, I have 10 a3s, 7 a1s, and 1 a2. All are configured to recieve a3 WUs. On the native Linux rigs configured for a3, one has an a2 and one has an a1.

[mrfrankmrfrank]

Well, I'll have to keep an eye out each time I go to this guys house to see if he ever gets an a/2 a/3. I'l have to check his fahlog. Him and I aren't the closest of friends so I don't see him that often. Perhaps before I get over to his house again I'll notice an increase in his ppd output. If he manages to get a core that can run more threads, I'm sure his ppd output will be over the average of 2000 that he has been getting now.

[mrfrankmrfrank]

I hope nobody punts me in the face for asking this question, but what exactly does a bigadv unit look like. How do you know you've had one. Is it simply an a/3 core with more points? Is it a different core altogether? The only reason I ask, as in preparation for my friend's mac to eventually be deserving of a bigadv unit, I'd like to know what it looks like when he gets one.

:screwy:

[ChasR]

p2681 through p2683. Base value 25,403 points. Uses 3.5 GB of ram. Tahes 2 to 3 days on fast rigs,

[mrfrankmrfrank]

thanks for the tip

[mrfrankmrfrank]

well I finally got over to this guys house to re-setup his folding@home client.

I downloaded and configured the mac console client on his machine. I set up his username and his passkey. I set the unit size to big. I set it up as smp -16. I left off the -bigadv for now because he has yet to complete 10 a/2 a/3 units yet under his passkey.

I launched the client, and it downloaded an a/3 core. I checked the activity monitor and it was indeed, finally using all of his cores. The folding client / core was using 98% of his cpu power.

My plan is to wait until he has completed his required 10 units, then go back, shut off the -advmethods flag and add the -bigadv flag.

My only question/ problem is. I installed and launched fahmon on his machine, since I don't think there is a hfm.net client for mac, and he was only getting 1500ppd. How is a dual quad cpu xeon mac only getting 1500 ppd?

[HayesK]

I do not use fahmon, but suspect that it is not reflecting the bonus. With the work unit point value and frame time, the ppd can be estimated. I think there are some on-line calculators available.

HFM is showing 9.3-9.6Kppd for my clients with ~4.5 minute frame time on A3 wu.

[dark bishop]

HFM is the only monitor able to calculate bonuses so far.

[mrfrankmrfrank]

yes, but would bonuses be calculated even if he has -bigadv turned off. I thought you only had to worry about bonuses when you were working with -bigadv turned on.

[HayesK]

All wu with non-zero Kfactor have bonus dependent on how quickly the wu is completed. All the current A3 WU and the bigadv A2 WU. The base point and Kfactor are shown on the Stanford site http://fah-web.stanford.edu/psummary.html

[mrfrankmrfrank]

so is what you're saying is that fahmon is showing 1500 ppd but this is most likely inaccurate? If I were able to view the client through hfm it would more accurately provide what the machine is actually doing in terms of ppd?

[madhatter256]

HFM is the only monitor able to calculate bonuses so far.

It hasn't kicked in for me... HFM shows 900PPD for my phenom II 940 running A3 core. Has uploaded 12 A3 Work Units so far....

[Outback_Jon]

It hasn't kicked in for me... HFM shows 900PPD for my phenom II 940 running A3 core. Has uploaded 12 A3 Work Units so far....
Are you running 24/7? If so, are you sure that Folding is using using all that it can? I've got a couple of Phenom X3s that get more PPD than that.

I don't think HFM takes into account the 10 unit requirement, it just calculates the PPD based on the bonuses, unless you have it selected to not calculate bonuses.

Also make sure you are using the latest version of HFM. The bonus calculation is only included in the last few releases. Current version is v.0.4.9

[HayesK]

so is what you're saying is that fahmon is showing 1500 ppd but this is most likely inaccurate? If I were able to view the client through hfm it would more accurately provide what the machine is actually doing in terms of ppd?

Depends upon the wu and frame time (you have yet to share that info), but I suspect so. Here is a thread with link to bonus ppd calculators. http://www.overclockers.com/forums/showthread.php?t=632612

[mrfrankmrfrank]

I'd love to share that info as soon as I can get at it. Like I said, this is on a friend's mac pro. I might get there early this coming week and I'll get my hands on the fahlog and other goodies.

[ChasR]

It hasn't kicked in for me... HFM shows 900PPD for my phenom II 940 running A3 core. Has uploaded 12 A3 Work Units so far....

HFM has no clue whether you're bonus qualified or not. It calculates all the a3 and -bigadv WUs as if you are qualified, unless you alter the default by unchecking the calculate bonus ppd box in preferences. So the real issue is why you are only making 900 ppd. One reason could be turning the machine off. HFM doesn't base bonus ppd the same way it does on other WUs. Instead it uses whichever calculation method you select in preferences to predict a completion time, from which it subtracts the actual download start time to obtain a total WU time, which it uses to calc ppd.

[mrfrankmrfrank]

So, I really, truly confused myself. I finally got over to his house to throw the -bigadv switch on. He has been folding a3 cores for about 2 weeks and has been getting bonus points. He has been averaging 12,000 ppd on his processor. Today I reconfigured his client and took the advmethods off and added bigadv.

The part that confuses me is that I was under the impression that bigadv work units are a3 cores. He downloaded an a2 core and his activity monitor showed like 16 instances of the a2 core as opposed to the usual one or so instances of the a3 core.

I shared his work directory over to my laptop so I could monitor his client with hfm.net and it shows that it is core GROCVS, project 2683 (r9, c2, g48) with a credit of 25403.

I assume that this is in fact a bigadv unit based on its credit, but I thought it would be an a3 core.

[Bluefalcon13]

bigadv is A2, A3 is normal SMP w/ bonus points

[mrfrankmrfrank]

well how about that. you learn something new every day

[mrfrankmrfrank]

so maybe chasr knows this one. As if anyone has been following this thread. My buddy's mac was finally configured for the bigadv units. He finished one in 2.5 days and received roughly 60,000 points for it. I was expecting him to finish his second bigadv unit tomorrow afternoon some time. So I just checked his stats and in the last update according to kakaostats, he updated with 1 point. Yes, 1 point.

Does this mean that he was working on a bigadv unit that failed? I am not at his house and have no way of knowing what happened, but I've never seen an increase of 1 point before.

[ChasR]

EARLY_UNIT_END, and trashed the WU. It happens, but without the log, it's hard to know why.

[mrfrankmrfrank]

ahhh, two days assumed gone... sad day.

i'll have to head over to his house tomorrow and check his log. perhaps i'll upload it here.

as always, overclockers and chasr are top notch. Thanks for the help guys.

[Sneaky]

with all this F@H stuff, I'd really just like to see a picture of the inside of the machine besides the ones I can find on google images.