Didn't read all 4 pages so dunno if it was posted, but my F@H won't get the new core. :(
I delete the core_11.exe and restart fah, but it just downloads core_11 again. I did this 3 times already... :(
Printable View
Didn't read all 4 pages so dunno if it was posted, but my F@H won't get the new core. :(
I delete the core_11.exe and restart fah, but it just downloads core_11 again. I did this 3 times already... :(
Definitely not, it's for all nV cores. My GSO saw some 8% gain on project 5800 as I wrote here. Maybe your FahMon is acting up again? Did you set it to L3F for computing the PPD?Quote:
Originally Posted by [XC] Synthetickiller
That's absolutely correct, it still is core 11. You need to look carefully:Quote:
Originally Posted by gallardo
It's all good! :up:Code:[06:55:17] Core required: FahCore_11.exe
[06:55:17] Core found.
[06:55:17] Working on queue slot 06 [October 17 06:55:17 UTC]
[06:55:17] + Working ...
[06:55:17] - Calling '.\FahCore_11.exe -dir work/ -suffix 06 -priority 96 -checkpoint 15 -verbose -lifeline 3288 -version 620'
[06:55:17]
[06:55:17] *------------------------------*
[06:55:17] Folding@Home GPU Core - Beta
[06:55:17] Version 1.15 (Mon Oct 13 11:11:30 PDT 2008)
yep what he said, you've gotten the new core, same filename, just a new version :up:
how many SPs on that GPU? Perhaps improvement is relative to number of SPs? :shrug:Quote:
Originally Posted by [XC] Synthetickiller
It's got 96SP's, the new core definitely has an impact. :yepp:Quote:
Originally Posted by coo-coo-clocker
The general impression of the discussion over on the Stanford Folding forum is that with the new code they are trying to optimize and make overclocking of the card not as necessary for maximum ppd. As most can see by having to reduce their overclocking to remain stable while still seeing any improvement in ppd. The GPU2 client and folding is a ever evolving thing I doubt we have seen the final evolution yet.
Well since I removed the flag getting me those trouble projects it's been running fine again, even with the new core. Glad Voelz decided to pull them, but even then I had to remove the flag to ger rid of them still showing up ( must have been one of the latest ).
Yea those projects even with the beta flag have been pulled except for ones they have already put out and had comeback EUE so they are some still floating around. Lately I have been getting a pretty steady diet of 5800 wu's with the flag and I still get a few EUE's maybe 1 out of 10 wu's folded average which I do not think it too bad its heck of a lot better than the 40-50% I was getting when the 57xx projects were in being pushed full force.Quote:
Originally Posted by Marvin_The_Martian
Right.... it's all good! :D
Didn't think to check the log file... :doh:
I'm trying to update today and the client wants to download a new core, even though I manually replaced the old core w/ the new one along w/ the dll files. It will connect to the server and download, but says that there is a "core download error" every time.
Any ideas? :shrug:
Edit:
One of my GSOs is working fine. Downloaded and updated the core. It's getting 5057.56ppd STOCK. I just OC'd it and am awaiting the new ppd. My other GSO in the first slot will not update. I even tried copying the core from the other folder. No luck.
To upgrade, stop the client, delete only the old core, and let it auto download the new core. You other files should've been fine.
Of course, server issues on the other side isn't beyond the realm of possibility.
I had to copy and paste everything to a new folder. It wouldn't let me delete the actual core.Quote:
Originally Posted by Sir_Loin
Anyways, its working now. :up:
I'd advise everyone to check their logs for UNSTABLE_MACHINE instances...
I went thru all 4 gpu clients, both logs:
FAHlog.txt
FAHlog-Prev.txt
and did a find for "UNSTABLE_MACHINE"
8 logs, 5 days and 11 eue's...
these cards run 24/7, and crank out like 10 wu's a day each.
so I know that's not alot, but still... a 5-10% eue rate..
so I went down a notch on all my cards shader oc.
8800gt's and 9800gt is now 1728
9600gso is now 1674
see if it helps any... dunno, it may just be the new core. but I don't remember seeing this many before with the old core.
Do you run ****? I asked for my thread here to be deleted because my errors where all related ( excluding two exceptions but they where spread out enough to be coincidental ) to only those projects.Quote:
Originally Posted by MikeB12
no, I've never run that on the gpu clients. just smp. my gpu clients are just normal no flag clients. I saw your thread, but didn't know why it was eueing until shadow mentioned it.. afterwards, I looked in the beta forum and saw what yall were talking about.
Lol I keep forgetting that... I mean everyone who I know who folded for some time knows the flag, when I started on fm people used it to boost ppd everywhere. Now it's less beneficial, well atleast not always :) If you pay enough attention you won't get the issues I had ( 11 eue's in 3 days ).
I got banned from the forum once for making an installer which exposed the flag as a normal setup option :)
Btw, been working..
http://img369.imageshack.us/img369/6...etupba1.th.pnghttp://img369.imageshack.us/images/thpix.gif
http://img528.imageshack.us/img528/8...nfigwn3.th.jpghttp://img528.imageshack.us/images/thpix.gif
yeah, just thought I'd mention it since 7im slapped me for it recently. I really dont know why some of that stuff is so secretive.. but it's their project and forum, so their rules.. whatcha gonna do.. as the old saying goes..
Same feeling here, though I must say they changed allot in how they deal with it. Seems allot of newer people don't know the flag. I think two things are responcible, most importantly using it mostly brings trouble but also the added value has dropped on it's own, both responcible for not many teams openly admitting to all using the flag ( which is how I remember it from the 'old' days ). I would rather see them make the flag public but add a check in the client to see if you have the elevated forum rights ( and responcibilities.. I forgot that last week :down: ) so it won't be of any use if you don't have shown the intrest in what the flag is supposedly used for.
Wow Mike, my 8800GT's run 1812 Shaders, no eue's:up:Quote:
Originally Posted by MikeB12
1836 used to be stable on core 1.09, it's not on core 1.15
my shader stops are 1782 or 1836... I can set it on whatever and it'll just round it off to the next hop.... are you sure it's 1812?
Lol Dak yeah that's old news, didn't know you wouldn't know :rofl: ;)
http://foldingforum.org/viewtopic.php?f=52&t=6552
Does not fix the 5801 issue, more info is in the thread :)Quote:
No showstoppers were found during the beta testing of v1.18, but we do not want to force a core upgrade at this time. If you are having problems with v1.15, please try replacing it with this newer version. It can be downloaded from http://www.stanford.edu/~friedrim/FahCore_11.exe. Thanks.
Did anyone backup their 1.09 to test if 5801 is stable on them like Pande said? I'm not at home atm so I wouldn't know if they're still being sent out.
Where did he say that? 5801 is taken down because it was unstable with all cores, 5800 went through QA on 1.09 I think you mean and 5801 is almost a copy ( or is a copy? ) so their abit stumped on how it happend.Quote:
Originally Posted by p2501
That's what I can make of it?
Oh I think the link was in the let's-all-complain-about-p5801-thread. I think, but I'll check later. I'm not mixing up things then Vijai or whoever answered to a post complaining about fail at QA generally, saying that those in fact might have been checked with an earlier core then 1.15. His statement was very vague though.Quote:
Originally Posted by Marvin_The_Martian
Right. New Core 1.18. Is it better? Will the client auto Download it? Do I have to manually download it? Waaa.
Manual download Riptide, seems to be abit better for some and the same for others. Don't expect miracles :(
IN my case... WU time back up to 1min 10Secs. On 8800GTX. Bad for me. Thast 4 seconds longer. = ~200 PPD.Quote:
Originally Posted by Marvin_The_Martian
You're the first I think who reported this happening :confused: *goes to check
*Edit: nope:
http://foldingforum.org/viewtopic.ph...tart=15#p64806
Ya same project too! 5506.
I also note Mike wiped the content of the 1st post in this thread. :( Waaa. he should have kept it as a historic log.
I made a thread about this new core but removed it and pm'd it to Mike.
If you ask Mike if he's willing to do it, you 'could' change the thread title to "Nvidia gpu cores discussion" and we can ask Mike to edit the first post with links containing post numbers so people can navigate through the thread to the proper core from post one? Just an idea, think it would be very handy to keep things organized and clean ( like, not x number of threads on nvidia cores ). Ideally we should have a thread about the Ati client as well, and one dedicated to the smp clients ( I don't mean the guides, just discussion threads ). Not even sure if we already have them, think I might have overlooked them if we do but it would prevent me for instance creating a new thread about every core coming out.
.002?
1.18 still EUEing my 8600gt instantly. Ughn, its gotta be something with server 2008 or my setup, my other 8600gt was running perfectly fine on my other system as a secondary card. Maybe I'll just completely uninstall it all and start over. Is there a gpu CLI version?
Maybe this would be a good time to try out your installer Marvin? Care to share?
yeah, I just replaced the op with 1.18 info....
the only thing that was in the op was the links to the old core threads at fah.... I can put those back, but it's old info now...
my ppd and frame info is in post #2 and #5 under the op if you still need 1.15 data. even some old data from 1.09 core....
Riptide, you can edit the op however you see fit.. I figured since this thread was a sticky we'd just make it the "new gpu core" thread and keep updating the op with the new cores. fah has been burning thru these cores like a bat out of hell.. in fact I tried to change the thread title to just "new gpu cores", but it only changed it inside the thread, not from the forum menu side.
Do we need to go at this again :rofl:Quote:
Originally Posted by MikeB12
I appriate the hard work you're doing so I'll not make an issue out it this time :nono:
;)
*Just to make sure, this time I'm joking about the semantics :)
Quote:
Originally Posted by MikeB12
politics :rolleyes:
removed all the I's and replaced one with "marvin"...
It's all good Mike, I talk allot but I'm doing far less for this team then you and you deserve the praise for the hard work :up:
:hump: :hump: :hump:
awww.... lets all have a group cuddle. :lol:
:hump: is much nicer, it shows how I really feel..
:yepp:
Is anyone actually seeing a points increase with core 1.18?? After yesterdays fiasco, I feel like just letting my machines run for a few days. I may try it on on 9800GX2 that was problematic yesterday. :)
About the same here but I can't compare it with a proper reference project, think you need to wait for someone with a larger hw arsenal to try and give some conclusive answers. It's not supposed to give a ppd increase btw, it's supposed to cut down eue rate ( which will make you turn in more ppd anyway ).
Everything moves past 5801 now. Do I need to worry about it coming back or is has that WU been pulled for more testing?
Pulled! Thank god :wave:
Maybe I can get back up to 40kPD now. God!
Did you get your 96GSOs in yet? You ordered two, right? We need to catch up from this weekend. Whiskey got its butt kicked.
In that case, I'll upgrade only the GPUs that exceed their 24hr EUE limit. :up:Quote:
Originally Posted by Marvin_The_Martian
Their coming... no set date yet :)Quote:
Originally Posted by MaK2000
WFO I'm not sure btw, it could be that you'll see improvements with the new core on some wu's and not on others, it might be better optimized for the larger wu's vs the smaller wu's. So it will still depend on what wu's they run if the optimisations did favour the larger wu's.
Okay I have both clients folding on 1.18 and they're doing fine for about 10hrs now. If that continues it maybe I'll forget about the last few days.
Gpu core 1.19 available
http://www.stanford.edu/~friedrim/FahCore_11.exe.
edit: Back to 1.09 speeds for me
Rip should really have merged the thread... Sorry oldchap old news ;)
Still..... no harm, just did not see it here......I only visit your folding forum to see the BIG fish at work occasionally....I fold in a smaller pondQuote:
Originally Posted by Marvin_The_Martian
Luck to you all :up:
No you're welcome and it's appriciated. Was more a hint to someone else, as it would have saved you the troubles :up:Quote:
Originally Posted by OldChap
And we're not all big fish btw, think I'm comparable with http://nexus404.com/Blog/wp-content/...3/goldfish.jpg
We would be happy to have you swim among us :wave:
Thanks MtM, but I'm happy to stay Pure. They are a good bunch even if most don't stick with folding (and they call me grumpy!)
Ow but we're a good bunch to :buddies:
But hey, you don't have to be on our team to get my respect, if there is ever anything I can do for you just let me know :)
Slower than 1.15 for sure... Now where the heck did I put the bookmark of the manual download page, I need 1.15 back...Quote:
Originally Posted by OldChap
Pip old chap! I see you decided to join us :D
PM Kondik if you can't find it :)Quote:
Originally Posted by road-runner
Hate other people getting quoted for stuff I post here only because someone has a problem reading it seems :shrug:
That's not aimed at you RR :up:
Edit* I'll put what I posted before in this post just for 'completeness'
Thanks for looking :wave:Quote:
Originally Posted by Marvin_The_Martian ;)
RR i have the 1.15 saved , I used the new 1.18 and 1.19 but they are ... ummm ... my VGA does 1% around 50 ~ 55 sec , with 1.18 and 1.19 it's over 64 seconds ...
my ppd went down by a solid amount, back to 1.15
Thanks, I was not thinking when I posted that. I had 1.15 on my other rigs, just opened the folder and got a copy...Quote:
Originally Posted by Kondik
Now I know the answer to this is probably in 10 different threads on here, but I'm feeling tired and lazy right now, too much folding fluid this evening I guess...
For dual GPU folding on a C2D rig, I know I cannot use AC to "do the magic" to balance the two fah cores across the two CPU cores. I went in and manually assigned them, but I also recall that when each WU finishes, that instance of the fah core shuts down and a new starts up upon the new WU arrival. How does one go about making a lasting fix on this?
I been trying to get people to use thisQuote:
Originally Posted by coo-coo-clocker
http://sourceforge.net/project/platf...roup_id=238550
As it has built in core logic, you can make sure smp is on the same die, and have two cores for gpu folding/other things.
Thanks for the link, Marvin. Great program!! :up:
If you like and play with it, I think the whole team could benefit if you showed us some examples about how to use it and how big if any the benefits are :up:Quote:
Originally Posted by coo-coo-clocker
I couldn't because of my os and hw I'm running, no much sense in starting a thread about it if I can't show the benefits. But it should really help with smp's because you will loose fsb traffic using two cores on the same die I would expect.
Well, I was using fahwatch to look through my logs at old WU's I've done, and apparently I did a 5748 and didn't even notice it. Now I've got both 1.15 and 1.19. I guess they renamed core 1.19 to FahCore_13.exe so that it wouldn't overwrite the old core? Any way of telling how many points I got for that WU?
Code:Os version: Microsoft Windows NT 6.0.6001 Service Pack 1
User: JOELZ0R\Administrator
Account: Administrator
---------------------------------------------------------------------------------
-FAHMON NAME: GTX260 - Desktop
INDEX: 1
LOCATION: C:\Users\Administrator\AppData\Roaming\Folding@home-gpu\
LOCAL CLIENT: True
CLIENT: Windows GPU Console Edition - Folding@Home Client Version 6.20r1
FLAGS: -gpu 0
CORE: Folding@Home GPU Core - Beta - Version 1.19 (Thu Oct 23 10:15:05 PDT 2008)
StartTime: 08:01:03
StartPercentage: 1
EndTime: 10:38:43
EndPercentage: 100
-VIDEO CARD
Caption NVIDIA GeForce GTX 260
Description NVIDIA GeForce GTX 260
AdapterRam 896MB
DriverVersion 7.15.11.7824
DriverDate 20081007173300.000000-000
Index 0
InfSection nv_GT2x
COMPILER: Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
BUILDHOST: amoeba
BOARD: Nvidia
PROJECT: Project: 5748 (Run 1, Clone 115, Gen 2)
QUEUESLOT: Working on queue slot 06 [November 6 03:19:15 UTC]
CORESTATUS: CoreStatus = 64 (100)
TIMESTAMP: [10:38:56]
if you completed it you got 511.. but if you wanna see your ppd, look at fahmon.. menu-benchmarks.
There is also a project browser in fahwatch :) Options, project browser :up: Fahcore_13 getting assigned to everyone was a glitch I think, since it should be a beta only core :)
lol...fahmon didn't really have much to say:
Project : 5748 (Unknown)
-- GTX260 - Desktop --
Min. Time / Frame : 1mn 34s
Avg. Time / Frame : 1mn 34s
Cur. Time / Frame : 1mn 35s
R3F. Time / Frame : 1mn 34s
Eff. Time / Frame : 1mn 34s
And nice touch Marvin. I like that project browser.
that's 4696ppd cat.. very good...
my 8800/9800gt's got 3500ppd
sp's obviously make a big difference in larger atom wu's.. guess I need to uncheck "larger wu's" in my clients. if that even matters.
Shouldn't matter Mike, gpu currently has no disctinction between wu sizes. Those 12xx atoms you will get even with small wu's ( and btw it's not the atom count but the upload size of the completed wu's ).
dam :down:Quote:
Originally Posted by Marvin_The_Martian
Yeah you think I like getting those big wu's with a 64shaders card? Ow no wait I beta test. I'll always get the largest wu's I think :rofl:
Whoa, workin on 5014 now and fahmon is showing its ppd up to 7.5k. Awesome. Keep those 5014's rollin in.
i keep getting stuck with 5506's really throwing my total PPD down a good 2k points using 1.19... oh well, i guess thats what happens in the wonderful world of folding...
Can we still use 1.15???
just delete your core dak. and let the client dl one. there still sending the optimized core..
can I do it while it's already in the middle of a WU?
sure, just stop the client, delete the core/s, and restart it..
New Core 14. Report findings. :)
Stuttering. Outlandish points and fluctuations.
Projekt : 5900
Core : Unknown
Frames : 100
Punkte : 420
-- 295-G0 --
Minimale Frame-Dauer : 37s - 9807.57 ppd
Gemittelte Frame-Dauer : 44s - 8247.27 ppd
Aktuelle Frame-Dauer : 51s - 7115.29 ppd
L3F-Frame-Dauer : 49s - 7405.71 ppd
Effektive Frame-Dauer : 48s - 7560.00 ppd
-- 295-G1 --
Minimale Frame-Dauer : 25s - 14515.20 ppd
Gemittelte Frame-Dauer : 32s - 11340.00 ppd
Aktuelle Frame-Dauer : 25s - 14515.20 ppd
L3F-Frame-Dauer : 35s - 10368.00 ppd
Effektive Frame-Dauer : 38s - 9549.47 ppd
Near 15k PPD from one core.
I set -advmethods on one 8800GS on a dedicated cruncher. Will see if it gets a 5900 and core 14 and see how it does.
I cleared benchmarks.dat so these are on one right now. and they are picking them up with no -advmethods now..
Project : 5900
Core : Unknown
Frames : 100
Credit : 420
-- X4-GPU2-8800GT-1782 --
Min. Time / Frame : 1mn 33s - 3901.94 ppd
Avg. Time / Frame : 1mn 33s - 3901.94 ppd
Cur. Time / Frame : 1mn 33s - 3901.94 ppd
R3F. Time / Frame : 1mn 33s - 3901.94 ppd
Eff. Time / Frame : 1mn 32s - 3944.35 ppd
-- X3-GPU1-9600GSO-1728 --
Min. Time / Frame : 1mn 36s - 3780.00 ppd
Avg. Time / Frame : 1mn 36s - 3780.00 ppd
Cur. Time / Frame : 1mn 36s - 3780.00 ppd
R3F. Time / Frame : 1mn 36s - 3780.00 ppd
Eff. Time / Frame : 1mn 38s - 3702.86 ppd
-- X5-GPU2-9800GX2-1783 --
Min. Time / Frame : 1mn 14s - 4903.78 ppd
Avg. Time / Frame : 1mn 14s - 4903.78 ppd
Cur. Time / Frame : 1mn 14s - 4903.78 ppd
R3F. Time / Frame : 1mn 14s - 4903.78 ppd
Eff. Time / Frame : 1mn 14s - 4903.78 ppd
Like the avatar Mike...Well, what's the verdict on this new core???
Since these started I've had a couple of instances of my rig re-starting but I'm not sure that this is related.
My numbers....
Code:Project : 5900
Core : Unknown
Frames : 100
Credit : 420
-- 260-1 --
Min. Time / Frame : 56s - 6480.00 ppd
Avg. Time / Frame : 57s - 6366.32 ppd
Cur. Time / Frame : 1mn 02s - 5852.90 ppd
R3F. Time / Frame : 1mn 02s - 5852.90 ppd
Eff. Time / Frame : 1mn 08s - 5336.47 ppd
-- 260-2 --
Min. Time / Frame : 55s - 6597.82 ppd
Avg. Time / Frame : 59s - 6150.51 ppd
Cur. Time / Frame : 1mn 06s - 5498.18 ppd
R3F. Time / Frame : 1mn 06s - 5498.18 ppd
Eff. Time / Frame : 1mn 33s - 3901.94 ppd
-- gx2-1 1 --
Min. Time / Frame : 56s - 6480.00 ppd
Avg. Time / Frame : 1mn 01s - 5948.85 ppd
No Cur. Time / Frame
No R3F. Time / Frame
No Eff. Time / Frame
-- gx2-1 2 --
Min. Time / Frame : 53s - 6846.79 ppd
Avg. Time / Frame : 1mn 06s - 5498.18 ppd
No Cur. Time / Frame
No R3F. Time / Frame
No Eff. Time / Frame
-- gx2-2 1 --
Min. Time / Frame : 1mn 00s - 6048.00 ppd
Avg. Time / Frame : 1mn 06s - 5498.18 ppd
Cur. Time / Frame : 1mn 08s - 5336.47 ppd
R3F. Time / Frame : 1mn 08s - 5336.47 ppd
Eff. Time / Frame : 1mn 09s - 5259.13 ppd
-- gtx --
Min. Time / Frame : 1mn 04s - 5670.00 ppd
Avg. Time / Frame : 1mn 09s - 5259.13 ppd
No Cur. Time / Frame
No R3F. Time / Frame
No Eff. Time / Frame
-- GX2-2 2 --
Min. Time / Frame : 1mn 07s - 5416.12 ppd
Avg. Time / Frame : 1mn 10s - 5184.00 ppd
No Cur. Time / Frame
No R3F. Time / Frame
No Eff. Time / Frame
8800GS is 3500 PPD right now.
Almost 24hrs since I put the -advmethods flag in all my gpu clients. Fahmon is showing an average of about 16k pd increase for 14 clients. :p: I can only hope that's accurate! :yepp: I think it is. I'm already at 85K with 2 updates. Hopefully 115K + for today. :p:
Code:Project : 5900
Core : Unknown
Frames : 100
Credit : 420
-- 9450-1 gpu 0 --
Min. Time / Frame : 1mn 24s - 4320.00 ppd
Avg. Time / Frame : 1mn 25s - 4269.18 ppd
Cur. Time / Frame : 1mn 47s - 3391.40 ppd
R3F. Time / Frame : 1mn 51s - 3269.19 ppd
Eff. Time / Frame : 1mn 46s - 3423.40 ppd
-- 9450-1 gpu 1 --
Min. Time / Frame : 1mn 14s - 4903.78 ppd
Avg. Time / Frame : 1mn 25s - 4269.18 ppd
Cur. Time / Frame : 1mn 32s - 3944.35 ppd
R3F. Time / Frame : 1mn 32s - 3944.35 ppd
Eff. Time / Frame : 1mn 35s - 3819.79 ppd
-- 9450-2 gpu 0 --
Min. Time / Frame : 56s - 6480.00 ppd
Avg. Time / Frame : 1mn 00s - 6048.00 ppd
Cur. Time / Frame : 1mn 11s - 5110.99 ppd
R3F. Time / Frame : 1mn 10s - 5184.00 ppd
Eff. Time / Frame : 1mn 13s - 4970.96 ppd
-- 9450-2 gpu 1 --
Min. Time / Frame : 42s - 8640.00 ppd
Avg. Time / Frame : 51s - 7115.29 ppd
Cur. Time / Frame : 1mn 15s - 4838.40 ppd
R3F. Time / Frame : 1mn 15s - 4838.40 ppd
Eff. Time / Frame : 1mn 15s - 4838.40 ppd
-- 9450-2 gpu-2 --
Min. Time / Frame : 1mn 05s - 5582.77 ppd
Avg. Time / Frame : 1mn 05s - 5582.77 ppd
Cur. Time / Frame : 1mn 18s - 4652.31 ppd
R3F. Time / Frame : 1mn 15s - 4838.40 ppd
Eff. Time / Frame : 1mn 15s - 4838.40 ppd
-- 9450-2 gpu 3 --
Min. Time / Frame : 1mn 04s - 5670.00 ppd
Avg. Time / Frame : 1mn 05s - 5582.77 ppd
Cur. Time / Frame : 1mn 16s - 4774.74 ppd
R3F. Time / Frame : 1mn 15s - 4838.40 ppd
Eff. Time / Frame : 1mn 13s - 4970.96 ppd
-- G0-4-gpu 0 --
Min. Time / Frame : 58s - 6256.55 ppd
Avg. Time / Frame : 58s - 6256.55 ppd
Cur. Time / Frame : 1mn 02s - 5852.90 ppd
R3F. Time / Frame : 1mn 02s - 5852.90 ppd
Eff. Time / Frame : 1mn 03s - 5760.00 ppd
-- G0-4 gpu 1 --
Min. Time / Frame : 33s - 10996.36 ppd
Avg. Time / Frame : 2mn 23s - 2537.62 ppd
Cur. Time / Frame : 1mn 26s - 4219.53 ppd
R3F. Time / Frame : 1mn 29s - 4077.30 ppd
Eff. Time / Frame : 1mn 32s - 3944.35 ppd
-- G0-4 gpu-2 --
Min. Time / Frame : 47s - 7720.85 ppd
Avg. Time / Frame : 57s - 6366.32 ppd
Cur. Time / Frame : 59s - 6150.51 ppd
R3F. Time / Frame : 59s - 6150.51 ppd
Eff. Time / Frame : 1mn 15s - 4838.40 ppd
-- G0-4 gpu 3 --
Min. Time / Frame : 56s - 6480.00 ppd
Avg. Time / Frame : 57s - 6366.32 ppd
Cur. Time / Frame : 1mn 09s - 5259.13 ppd
R3F. Time / Frame : 1mn 09s - 5259.13 ppd
Eff. Time / Frame : 1mn 09s - 5259.13 ppd
-- G0-2-gpu-0 --
Min. Time / Frame : 1mn 28s - 4123.64 ppd
Avg. Time / Frame : 1mn 31s - 3987.69 ppd
Cur. Time / Frame : 1mn 44s - 3489.23 ppd
R3F. Time / Frame : 1mn 39s - 3665.45 ppd
Eff. Time / Frame : 1mn 38s - 3702.86 ppd
-- G0-2 gpu 1 --
Min. Time / Frame : 1mn 29s - 4077.30 ppd
Avg. Time / Frame : 1mn 31s - 3987.69 ppd
Cur. Time / Frame : 1mn 36s - 3780.00 ppd
R3F. Time / Frame : 1mn 39s - 3665.45 ppd
Eff. Time / Frame : 1mn 39s - 3665.45 ppd
-- I-7 gpu 0 --
Min. Time / Frame : 26s - 13956.92 ppd
Avg. Time / Frame : 39s - 9304.62 ppd
Cur. Time / Frame : 49s - 7405.71 ppd
R3F. Time / Frame : 47s - 7720.85 ppd
Eff. Time / Frame : 46s - 7888.70 ppd
-- AMD 0 --
Min. Time / Frame : 1mn 01s - 5948.85 ppd
Avg. Time / Frame : 1mn 02s - 5852.90 ppd
Cur. Time / Frame : 1mn 13s - 4970.96 ppd
R3F. Time / Frame : 1mn 11s - 5110.99 ppd
Eff. Time / Frame : 1mn 11s - 5110.99 ppd
-- AMD 1 --
Min. Time / Frame : 58s - 6256.55 ppd
Avg. Time / Frame : 1mn 02s - 5852.90 ppd
Cur. Time / Frame : 1mn 19s - 4593.42 ppd
R3F. Time / Frame : 1mn 16s - 4774.74 ppd
Eff. Time / Frame : 1mn 17s - 4712.73 ppd
-- AMD 2 --
Min. Time / Frame : 58s - 6256.55 ppd
Avg. Time / Frame : 1mn 01s - 5948.85 ppd
Cur. Time / Frame : 1mn 12s - 5040.00 ppd
R3F. Time / Frame : 1mn 16s - 4774.74 ppd
Eff. Time / Frame : 1mn 10s - 5184.00 ppd
-- AMD 3 --
Min. Time / Frame : 1mn 01s - 5948.85 ppd
Avg. Time / Frame : 1mn 02s - 5852.90 ppd
Cur. Time / Frame : 1mn 19s - 4593.42 ppd
R3F. Time / Frame : 1mn 12s - 5040.00 ppd
Eff. Time / Frame : 1mn 11s - 5110.99 ppd
-- I-7 gpu 1 --
Min. Time / Frame : 27s - 13440.00 ppd
Avg. Time / Frame : 39s - 9304.62 ppd
Cur. Time / Frame : 44s - 8247.27 ppd
R3F. Time / Frame : 45s - 8064.00 ppd
Eff. Time / Frame : 42s - 8640.00 ppd
-- G0-3 gpu 1 --
Min. Time / Frame : 39s - 9304.62 ppd
Avg. Time / Frame : 1mn 16s - 4774.74 ppd
Cur. Time / Frame : 1mn 56s - 3128.28 ppd
R3F. Time / Frame : 1mn 51s - 3269.19 ppd
Eff. Time / Frame : 1mn 58s - 3075.25 ppd
-- G0-3-gpu-2 --
Min. Time / Frame : 1mn 07s - 5416.12 ppd
Avg. Time / Frame : 1mn 16s - 4774.74 ppd
Cur. Time / Frame : 1mn 40s - 3628.80 ppd
R3F. Time / Frame : 1mn 50s - 3298.91 ppd
Eff. Time / Frame : 1mn 39s - 3665.45 ppd
-- G0-3 gpu 3 --
Min. Time / Frame : 1mn 08s - 5336.47 ppd
Avg. Time / Frame : 1mn 09s - 5259.13 ppd
Cur. Time / Frame : 1mn 14s - 4903.78 ppd
R3F. Time / Frame : 1mn 13s - 4970.96 ppd
Eff. Time / Frame : 1mn 12s - 5040.00 ppd
-- G0-3 gpu 0 --
Min. Time / Frame : 1mn 04s - 5670.00 ppd
Avg. Time / Frame : 1mn 07s - 5416.12 ppd
Cur. Time / Frame : 1mn 13s - 4970.96 ppd
R3F. Time / Frame : 1mn 12s - 5040.00 ppd
Eff. Time / Frame : 1mn 14s - 4903.78 ppd
I'm about ready to put advmethods on all mine. Been going smoothly on the one 8800GS so far. Sure it scores lower than some of the 300-something point units, but those are few, usually I get the 511s which drop down to under 3000 ppd. So a consistent 3550 ppd per card isn't bad at all. CPU usage is still 0% typically (XP) and temps are much lower too.
Hmmm, not so good:
Project:5900, Core:Unknown, Frames:100, Credit:420
-- 8800 GT 1728 Drv 180.48 --
Avg. Time / Frame : 1mn 42s - 3557.65 ppd
-- 9800 GX2 1716 Drv 182.6 --
Avg. Time / Frame : 1mn 18s - 4652.31 ppd
-- 9800 GX2 1716 Drv 182.6 --
Avg. Time / Frame : 1mn 19s - 4593.42 ppd
I think I'm doing better with more 5768s.. :)
That 5900 project is nuts tbh
From 7000 PPD to 10.000 on one card ... flies up and down like a poop in a tornado ...
One WU from this project is done in an hour and heats the card to 68 degrees , one takes double the time and heats the card to 85 degrees celsia
and both are 420 points .... what the eck ?
poop in a tornado :rofl:
Mike explained the "poop in a tornado effect" in the last race with the benchmark dart board. :rofl::rofl::rofl:Quote:
Originally Posted by Kondik
Kondik are you sure it was 5900? It should not take double the time, not even close, variations could be 25% or so :shrug: Also the temperature does not fluctuate like that with this same wu. It sound like you got another WU like the 5900 you're not supposed to get at this time :)
Which also explains why your scores are acting like poop in a tornado ;)
lol, WFO, I guess the correct term now is "Poop darts in a tornado"..
Remember kids, in tornado even a poop can be a deadly projectile that can blast a hole in a tank ! Deadly Poop ...
Noticed that this weekend my Nvidia GPU clients went from Core 11 to Core 14.
Have not had problems.
Is everyone else with Nvidia Windows clients seeing the version 14 cores?
There are 2 cores in use core 11 and core 14. However, core 11 is now in 2 flavours the original, which runs your cards hot and a variant http://www.stanford.edu/~friedrim/FahCore_11.exe which you can read about at http://foldingforum.org/viewtopic.php?f=52&t=10404 It is supposed to alow you to reduce gpu run time in order to control temps (have not really tried yet)
Found the answer to the core 11 or 14.
http://foldingforum.org/viewtopic.php?f=52&t=10128Quote:
Core 14 doesn't produce more science, it produces different science... otherwise all the projects would be using that core already. Suggesting replacing Core 11 with Core 14 is like replacing CPU Core 78 (the boggo Gromacs core) with CPU Core 80 (the Gromacs SREM core)... they serve different purposes even if they're based on the same package.
So core 14 is not an improvement on 11, it is just designed to run different projects.
GPU3 CORE
i haven't found anything posted in here about the GPU3 core for fermi gpus... are there no other folders with fermi cards?!?
Stanford GPU3 thread
Quote:
We have a new GPU core (core 15) going into an open beta test for NVIDIA clients. This core requires a new client (see below) as well as the latest drivers (197.45). This core is the first run of the GPU3 technology, derived from the OpenMM project at Stanford (http://simtk.org/home/openmm). You can find more information in our GPU3 FAQ (see url below).
While this release is for NVIDIA only to start, we are actively pushing ATI support (with the help of AMD/ATI), although we have no ETA at the moment. We do not recommend that you use this client with an ATI GPU at the moment since there is no advantage and you are potentially exposing yourself to new bugs.
This is the first open beta test of this new client and core, so there are likely bugs to be found as more donors try this out on more diverse sets of hardware. Also, the documentation (GPU3 FAQ) is new too and there are possibly some errors there too. However, the client has been QA'd both internally at Stanford and with our closed group of beta testers and is looking pretty good so far.
Some testers in the closed beta test have found problems with 8800 and 9800 class GPUs (we are working on this).