600 Point Gromacs!
Moderators: NeilBlanchard, Ralf Hutter, sthayashi, Lawrence Lee
-
- Posts: 542
- Joined: Mon Aug 11, 2003 5:54 pm
600 Point Gromacs!
600 Point Gromacs!
http://vspx27.stanford.edu/psummary.html
Has anybody gotten one of those WHOPPERS?
http://vspx27.stanford.edu/psummary.html
Has anybody gotten one of those WHOPPERS?
Yup, both of my boxes have been folding these 24/7 since Dec 20/21 - recieved 6 in a row so far (3 on each box). They complete in about 2.5 days on my Athlon XP's (2000 and 2200 MHz). Under normal conditions (no big WU bonus) I'd say I can barely make 200ppd. After submitting four of these, I was GREEN (400+ ppd 24hr average)!! Yayyy!!! I was even close to making the top 20 contributors list with just my two Athlon XP's. Really weird - or scary, depending on how you think about it. Needless to say that those 1200 points I received in one day is something I won't top in a while.
These beasts even seem to do some good to the production of our team: three consecutive days of 40k+ points, hadn't happened since early December (or is this just the usual fluctuation)? Surely boosted my production... Maybe a Xmas gift from Stanford?
They still don't have a description up on what the project is actually about.
EDIT: typos corrected
PS: unregistered: I'm due to overtake you in 571 days (if Stanford keeps the supply of 600 point Gromacs up 'til then) !
These beasts even seem to do some good to the production of our team: three consecutive days of 40k+ points, hadn't happened since early December (or is this just the usual fluctuation)? Surely boosted my production... Maybe a Xmas gift from Stanford?
They still don't have a description up on what the project is actually about.
EDIT: typos corrected
PS: unregistered: I'm due to overtake you in 571 days (if Stanford keeps the supply of 600 point Gromacs up 'til then) !
Last edited by JanW on Mon Dec 27, 2004 12:42 pm, edited 1 time in total.
Yep, here too - I think all of my boxes got them on the same day, because I had 36 hours of panic (0 WUs reported) and then a massive blast of 3000 points as 5 of them reported at the same time. Christmas day, no less! And I didn't even ask Santa for a boatload of points
btw! I'm dark red! I wonder how long it will last... Now if only I can get 3200 more points before 12/31 at 11:59 pm ...
btw! I'm dark red! I wonder how long it will last... Now if only I can get 3200 more points before 12/31 at 11:59 pm ...
Hmm, I just lost what was going to be the 11th of these 600 point units : it got deleted after 65% of the work done
Anyone had this happen, or any idea of what might be going on? I'm new to folding and this is the first WU I lose. Here's the interesting parts from the log:
Maybe I should start backing up my folding directory regularly...
Nothing particular happened at 22:31:28, that I'm aware of.
Anyone had this happen, or any idea of what might be going on? I'm new to folding and this is the first WU I lose. Here's the interesting parts from the log:
Code: Select all
[07:30:24] - Calling './FahCore_78.exe -dir work/ -suffix 00 -checkpoint 15 -forceasm -verbose -lifeline 17175 -version 502'
[07:30:24]
[07:30:24] *------------------------------*
[07:30:24] Folding@Home Gromacs Core
[07:30:24] Version 1.70 (October 24, 2004)
[07:30:24]
[07:30:24] Preparing to commence simulation
[07:30:24] - Assembly optimizations manually forced on.
[07:30:24] - Not checking prior termination.
[07:30:25] - Expanded 2910718 -> 16166533 (decompressed 555.4 percent)
[07:30:26] - Starting from initial work packet
[07:30:26]
[07:30:26] Project: 1135 (Run 8, Clone 26, Gen 0)
[07:30:26]
[07:30:26] Assembly optimizations on if available.
[07:30:26] Entering M.D.
[07:30:33] Protein: p1135_RIBO_FSpeptide_HEL
[07:30:33]
[07:30:33] Writing local files
[07:30:35] Extra SSE boost OK.
[07:30:35] Writing local files
[07:30:35] Completed 0 out of 250000 steps (0%)
[07:45:36] Timered checkpoint triggered.
[08:00:36] Timered checkpoint triggered.
[08:03:56] Writing local files
[08:03:56] Completed 2500 out of 250000 steps (1%)
... (a day and a half later) ...
[22:24:01] Completed 162500 out of 250000 steps (65%)
[22:31:28] CoreStatus = 0 (0)
[22:31:28] Client-core communications error: ERROR 0x0
[22:31:28] Deleting current work unit & continuing...
[22:32:21] Trying to send all finished work units
[22:32:21] + No unsent completed units remaining.
[22:32:21] - Preparing to get new work unit...
Nothing particular happened at 22:31:28, that I'm aware of.
-
- *Lifetime Patron*
- Posts: 1740
- Joined: Sun Dec 21, 2003 11:24 am
- Location: 'Sunny' Cornwall U.K.
Jan, there's a fair bit of info over at the F@H forums ref Error Codes 0x0 & 0x1, both seem to be only on linux and variants (incl. mac) and appear to be to do with 'incorrect shutting down sequence of the core'.
However I managed it this afternoon on XP by killing the wrong process in task manager . 50% through a 600 point WU that was then deleted ... and that was after an act of stupidity earlier in the week that cost me a full 600 points.
Pete
However I managed it this afternoon on XP by killing the wrong process in task manager . 50% through a 600 point WU that was then deleted ... and that was after an act of stupidity earlier in the week that cost me a full 600 points.
Pete
-
- Posts: 542
- Joined: Mon Aug 11, 2003 5:54 pm
Thanks peteamer and unregistered for your responses. I'll just wait for now and see if it happens again --- did install a cron job, though, that backs up my folding directory every three hours.
Over at F@H forums, I saw that Error 0x0 means that "the client doesn't really know what happened, except that it's serious" There seemed to be a lot of talk about glibc problems on Linux, but that was a while ago. It could also be simply instability, for example processor overheating. As the only thing I know about my XP temperature is that it is above 62C (placed a thermal probe right next to the core), that might be the problem... Had been stable for a month, though, running 24/7.
Ah, I guess the 100% big WU bonus we get on these is there for a reason: even after losing an occasional unit, I still want more of them
Which brings me on-topic again: folding number 11 and 12 right now (should be done tomorrow). So far 6000 of my 8740 points come from these biggies Just thought I'd share for those of you who wonder why you didn't get any
Over at F@H forums, I saw that Error 0x0 means that "the client doesn't really know what happened, except that it's serious" There seemed to be a lot of talk about glibc problems on Linux, but that was a while ago. It could also be simply instability, for example processor overheating. As the only thing I know about my XP temperature is that it is above 62C (placed a thermal probe right next to the core), that might be the problem... Had been stable for a month, though, running 24/7.
Ah, I guess the 100% big WU bonus we get on these is there for a reason: even after losing an occasional unit, I still want more of them
Which brings me on-topic again: folding number 11 and 12 right now (should be done tomorrow). So far 6000 of my 8740 points come from these biggies Just thought I'd share for those of you who wonder why you didn't get any
-
- Posts: 542
- Joined: Mon Aug 11, 2003 5:54 pm
62º is a little toasty. I have a rig that is similar to yours, except I have an XP2800(@2.09) and a Thermalright SP97/Panaflo92mmL1a(@~9v) combo(thermalrights are cool). According to Mbm5 CPU is 47º. I just vacumed the heatsinks with a crevice attachment, was 54º. Try MBM5, even though support was discontinued, it works on that board(mine same). Speedfan is also an option. I have it on my HTPC, it has more features, but I have had zero time to play with these things lately. I'm not sure if they have Linux versions. I have the same case without the intake fan, stock rear fan and PSU(loud), just one SATA 160 Spinpoint.
Sorry for drifting offtopic here...
Yes, unregistered, I found 62C outside the die to be on the hot side, too - and thanks for sharing your experience with that setup. I don't have a Windows license and have given up on reading the on-die diode under Linux for my board, so this is the only info I have.
Having tried around a little, I don't see how to improve things right now. Turning up the voltage on the CPU fan doesn't gain me much in temperature (for some odd reason), and the sacrifice in noise is just not worth it. Before someone suggests re-seating the HS, I'd add that I did that about a dozen times (no exaggeration!) and while I won't guarantee that it's seated perfectly, it's the best I can do.
My guess was that case air flow is suboptimal --- but your temperatures with a very similar setup seem to prove that wrong. Nevertheless, the case is due for the standard front-bezel mod, and I also have plans for a Bluefront-like PSU relocation (using a SuperTornado 300W), but I won't have time for that for a month or so.
Meanwhile I'm back to 62% on a 600 point WU on that rig. As long as WU losses don't become more frequent, I won't do anything about temperatures for now. It's just that, had these WU's been reported to be flaky, I could have blamed them But that doesn't seem to be the case
Yes, unregistered, I found 62C outside the die to be on the hot side, too - and thanks for sharing your experience with that setup. I don't have a Windows license and have given up on reading the on-die diode under Linux for my board, so this is the only info I have.
Having tried around a little, I don't see how to improve things right now. Turning up the voltage on the CPU fan doesn't gain me much in temperature (for some odd reason), and the sacrifice in noise is just not worth it. Before someone suggests re-seating the HS, I'd add that I did that about a dozen times (no exaggeration!) and while I won't guarantee that it's seated perfectly, it's the best I can do.
My guess was that case air flow is suboptimal --- but your temperatures with a very similar setup seem to prove that wrong. Nevertheless, the case is due for the standard front-bezel mod, and I also have plans for a Bluefront-like PSU relocation (using a SuperTornado 300W), but I won't have time for that for a month or so.
Meanwhile I'm back to 62% on a 600 point WU on that rig. As long as WU losses don't become more frequent, I won't do anything about temperatures for now. It's just that, had these WU's been reported to be flaky, I could have blamed them But that doesn't seem to be the case
-
- Posts: 542
- Joined: Mon Aug 11, 2003 5:54 pm
Use the "-config" flag when starting it to set processor utilization. Say "yes" to advanced options when prompted.
Example:
The "-configonly" option also allows configuration of the client, but exits after configuration is complete instead of proceeding normally.
Example:
Code: Select all
./FAH502-Linux.exe -config <other options, such as verbosity, advmethods, etc.>
-
- Posts: 542
- Joined: Mon Aug 11, 2003 5:54 pm
How much RAM do you have in that box? I think these peptide gromacs unlike typical WUs, are RAM demanding, it also sends a rather large results file.
That is slower than what I have been seeing on my 2800 or [email protected].
Ive noticed the WUs are not very consistent time/frames. Do you have something else runing in the background?
That is slower than what I have been seeing on my 2800 or [email protected].
Ive noticed the WUs are not very consistent time/frames. Do you have something else runing in the background?
Mine is also at 29 minutes per frame.. athlon 2600+, 1Gig ram. Oh, and i think you are right about these using a lot of memory, FahCore_78.exe is using 104720K of memory.. I assume this isnt common, i have not checked mem usage during other WUs so im not shure but it seems really high.
edit:typos..
edit:typos..
Last edited by nici on Wed Jan 12, 2005 11:07 am, edited 1 time in total.
-
- Patron of SPCR
- Posts: 2674
- Joined: Sun Jul 04, 2004 6:07 am
- Location: Houten, The Netherlands, Europe
Well these WU's aren't nicknamed BigWU's for nothing. And the 240MB minimum physical memory required to get them is for the same reason.
On my Hush: 104728K memory used by FahCore_78.exe.
On my P4 2.8: 104816K memory used by FahCore_78.exe.
On my P4 3.0: 103392K memory used by FahCore_78.exe.
This is why you get double the points for working on these WU's.
On my Hush: 104728K memory used by FahCore_78.exe.
On my P4 2.8: 104816K memory used by FahCore_78.exe.
On my P4 3.0: 103392K memory used by FahCore_78.exe.
This is why you get double the points for working on these WU's.
-
- Posts: 231
- Joined: Wed Apr 16, 2003 11:40 am
- Location: seattle, wa