Upcoming Release of SMP2 Cores

[LCB001]

Originally Posted by El_Fiendo

I'm noticing some issues where Core 14 specifically doesn't play well with Core A3. Sorry to sswilson, I thought my clients were fine. Everything Core 11 runs without throttling, but as soon as I get a Core 14 (or at least any that I've witnessed) all my GPUs slow down to 200 PPD (GSOs) and 400 PPD (GTX 260). Shutting down all clients and restarting the GPUs only does nothing, only deleting the work folder and queue.dat and getting a new work unit. It could be possible its a batch of bad work units as well. So far I've seen the issue with a couple different Core 14 work units.

Process Lasso is up to date, running strict management of priorities with Core 14 set to high priority. It has the same settings as Core 11, which all appear to be running fine with the SMP2 client open. I can't figure it out, but I'm going to shut down the SMP2 console and see if I can get a 'bad' Core 14 without SMP2 running. Has anyone else seen similar?

Kasson from the Pande Group just posted this on the F@H forums from this thread; Folding Forum • View topic - New client released - v6.29 Beta with -smp (SMP2 prequel!)

BTW, I just updated the Windows A3 core for auto-download. The new version shares processor time much better with other running processes but is a couple % slower on dedicated machines. We're working to combine the best of each version in the future.

I've had no issues so far on Rig1, Rig2 was having severe sharing problems until I updated the drivers (after almost a year and a half) to the 190.62`s like the other rigs which seems to have fixed things.

I won't be 100% sure until it gets another A3 Wu since it's Folding an A1 core (p2653) ATM, should know sometime tonight...

[El_Fiendo]

Originally Posted by LCB001

Kasson from the Pande Group just posted this on the F@H forums from this thread; Folding Forum • View topic - New client released - v6.29 Beta with -smp (SMP2 prequel!)
I've had no issues so far on Rig1, Rig2 was having severe sharing problems until I updated the drivers (after almost a year and a half) to the 190.62`s like the other rigs which seems to have fixed things.
I won't be 100% sure until it gets another A3 Wu since it's Folding an A1 core (p2653) ATM, should know sometime tonight...

Thank you! I'll keep an eye on that thread. My drivers are already 190.62s, but I hope you have better success with the rig you just updated. I was wondering if I should move up to the latest driver revision though. I didn't upgrade past 190.62 after seeing all the issues people were having, but perhaps the absolute latest might be something to look into.

[Zero82z]

The 2.15 core should deal with any resource hogging issues people have been having with SMP2. I've seen a significant improvement in system responsiveness since I started running it.

[LCB001]

Originally Posted by El_Fiendo

Thank you! I'll keep an eye on that thread. My drivers are already 190.62s, but I hope you have better success with the rig you just updated. I was wondering if I should move up to the latest driver revision though. I didn't upgrade past 190.62 after seeing all the issues people were having, but perhaps the absolute latest might be something to look into.

Which clients are you using, the only other difference between the two quad rigs is that Rig1's has two console clients vs two systray clients in Rig2. If the driver upgrade to Rig2 dosn't solve the problem changing it over to twin console's will be my next step. From his posts I think sswilson is also using the systray's which makes me wonder if there is some problem with them and the new SMP2 client co-existing.

Hopefully the tweaks that Stanford made to the A3 core will solve the problem and spare us all a little hassle.

@Zero82z; Just saw your post, thanks for the info I'll keep an eye out for it..

[martin_metal_88]

Originally Posted by MarkOne

Martin just drop this smp thing, go with the linux client in VMware. so easy to use, and with your 860 at 3.5 ghz you will get 20k a day ... don't let me overtake you in 4 days . fight my friend ...

Well mark I am using VM now I was just wonder if the SMP2 add the bonus possibility but the fact are that I can't do -advmethods using the linux VM because I only have 4Gigs of ram so if I want to run BigAdv it take all my 4091MB and my computer is slow as hell and my hard drive burn because he use it for memory. I will try to fight you back when I will have enough money to buy more memory. This could be long unfortunately.

[Zero82z]

Originally Posted by LCB001

From his posts I think sswilson is also using the systray's which makes me wonder if there is some problem with them and the new SMP2 client co-existing.

The systray client is identical to the console client outside of the interface. There are no problems with it and SMP2 coexisting.

[El_Fiendo]

Originally Posted by LCB001

Which clients are you using, the only other difference between the two quad rigs is that Rig1's has two console clients vs two systray clients in Rig2. If the driver upgrade to Rig2 dosn't solve the problem changing it over to twin console's will be my next step. From his posts I think sswilson is also using the systray's which makes me wonder if there is some problem with them and the new SMP2 client co-existing.

Hopefully the tweaks that Stanford made to the A3 core will solve the problem and spare us all a little hassle.

@Zero82z; Just saw your post, thanks for the info I'll keep an eye out for it..

I'm running 4 console clients on that system with little issue, I've never once installed a systray client. My GPUs used to see very little performance hit with all 4 running alongside the VMs. I'd lose about 200 PPD off each GPU in total between it running by itself, and it running with everything else at the same time.

Thanks LCB and Zero, hopefully this solves all of the issues.

[sswilson]

No systray client for me, it's strictly console.

Thanks for all of the updates folks. SMP is currently on hold until I get another chance to spend a couple of hours with it.

[boggtrotter59]

Set up the SMP2 client on a different machine, got it running but only showing 1212 PPD in Fahmon, WU is a 6012 470 points. I added the -smp -advmethods flag to the shortcut (everything else is default). Machine is running a Q6600 @ 3.2 Ghz. Any ideas why my PPD is so low, task manager shows all 4 cores going full tilt.

[sswilson]

Originally Posted by boggtrotter59

Set up the SMP2 client on a different machine, got it running but only showing 1212 PPD in Fahmon, WU is a 6012 470 points. I added the -smp -advmethods flag to the shortcut (everything else is default). Machine is running a Q6600 @ 3.2 Ghz. Any ideas why my PPD is so low, task manager shows all 4 cores going full tilt.

Because FAHmon doesn't factor in the bonus points.