The State of the SMX Project
I haven't been active with the team for the last 9 months or so, but that doesn't mean that I don't care what the team does either. I've seen that the SMX committee has been putting new machines out quite a bit lately, so I wanted to see what the SMX rigs are doing now. Here's what I've come up with, from the EOC stats.
SM1 - 81 POINTS/DAY AVG
SM2 - 0 POINTS/DAY AVG, Last WU returned 6/26/05
SM3 - 75 POINTS/DAY AVG
SM4 - 122 POINTS/DAY AVG
SM5 - 73 POINTS/DAY AVG
SM6 - 0 POINTS/DAY AVG, Last WU returned 10/18/05
SM7 - 0 POINTS/DAY AVG, Last WU returned 2/12/04
SM8 - 54 POINTS/DAY AVG
SM9 - 187 POINTS/DAY AVG
SM10 - 314 POINTS/DAY AVG
SM11 - 130 POINTS/DAY AVG
SM12 - 115 POINTS/DAY AVG
SM13 - 61 POINTS/DAY AVG
SM14 - 34 POINTS/DAY AVG
SM15 - 95 POINTS/DAY AVG
SM16 - 111 POINTS/DAY AVG
SM17 - 59 POINTS/DAY AVG
SM18 - 54 POINTS/DAY AVG
SM19 - 75 POINTS/DAY AVG
SM20 - 171 POINTS/DAY AVG
SM21 - 205 POINTS/DAY AVG
SM22 - 128 POINTS/DAY AVG
SM23 - 127 POINTS/DAY AVG
SM24 - 74 POINTS/DAY AVG
SM25 - 5 POINTS/DAY AVG
SM26 - 76 POINTS/DAY AVG
SM27 - 386 POINTS/DAY AVG
SM28 - 66 POINTS/DAY AVG
As you can see, there are a few inactive SMX machines. SM7 has been down for over a year due to an asshat stealing the original machine. I see that you guys have reassigned it to Crypto, who hopefully will have it up and running soon.:)
The second machine that is down is SM6, which hasn't turned in any work for half a month. I guess one of you SMX committee members needs to go over to Icrontic and PM Citrix to check the machine out.
Last we have SM2 that has been MIA since June of this year. Has anyone been able to get in touch with redoulent about why he hasn't had it up and folding? Red used to be one of our most steady hosts, but he is also one of the original hosts that refused to sign a contract too, after the first few machines were stolen. :shakehead I hope that nothing bad has happened to him, but I would hate to think he's turned into a frigging thief also.
Now, to the active machines, it looks to me like some of them are performing below their potential. After all, if you are going to foot the electric bill to keep it running, then why not maximize the points return for your bucks.
For AMD systems with the present work being sent out, set the machine up to do timeless wu's, which are all Tinker units now. Most of them are 239 pointers or 241 pointers and they give a good steady points return, much better on a Tbird or AXP processor than a regular Gromacs wu. I have both my remaining AXP machines configured this way and they return around 150-200 points/day/processor. This is with a NF7 rig at 2400 and a MP dually at 2133. Another plus is that the Tinker wu's are not ram or memory bandwidth intensive, which is great for older machines that have only 128 MB ram and/or SDRAM.
For P3 machines, Tinker work isn't the greatest choice. Setting it up to do regular Gromacs work is probably your best option, unless you have 512 MB ram onboard. Then you can try the -advmethods flag and hopefully grab some BigWU work.
For a P4 based machine, 512 MB ram and using the -advmethods flag with bigpackets=yes set in the config file. This will let the P4 grab QMD work, which requires 500 MB minimum ram. The point output difference is tremendous when a P4 can get QMD's. Just look at the points/day output of the P4 that Jon and Sally are hosting and then compare it to the one that dancer is hosting, which only has 256 MB ram. If you can get him another 256 MB stick of ram, that 1.6 P4 will be knocking on the heels of the fastest AMD systems the SMX project has running.
SM1 - 81 POINTS/DAY AVG
SM2 - 0 POINTS/DAY AVG, Last WU returned 6/26/05
SM3 - 75 POINTS/DAY AVG
SM4 - 122 POINTS/DAY AVG
SM5 - 73 POINTS/DAY AVG
SM6 - 0 POINTS/DAY AVG, Last WU returned 10/18/05
SM7 - 0 POINTS/DAY AVG, Last WU returned 2/12/04
SM8 - 54 POINTS/DAY AVG
SM9 - 187 POINTS/DAY AVG
SM10 - 314 POINTS/DAY AVG
SM11 - 130 POINTS/DAY AVG
SM12 - 115 POINTS/DAY AVG
SM13 - 61 POINTS/DAY AVG
SM14 - 34 POINTS/DAY AVG
SM15 - 95 POINTS/DAY AVG
SM16 - 111 POINTS/DAY AVG
SM17 - 59 POINTS/DAY AVG
SM18 - 54 POINTS/DAY AVG
SM19 - 75 POINTS/DAY AVG
SM20 - 171 POINTS/DAY AVG
SM21 - 205 POINTS/DAY AVG
SM22 - 128 POINTS/DAY AVG
SM23 - 127 POINTS/DAY AVG
SM24 - 74 POINTS/DAY AVG
SM25 - 5 POINTS/DAY AVG
SM26 - 76 POINTS/DAY AVG
SM27 - 386 POINTS/DAY AVG
SM28 - 66 POINTS/DAY AVG
As you can see, there are a few inactive SMX machines. SM7 has been down for over a year due to an asshat stealing the original machine. I see that you guys have reassigned it to Crypto, who hopefully will have it up and running soon.:)
The second machine that is down is SM6, which hasn't turned in any work for half a month. I guess one of you SMX committee members needs to go over to Icrontic and PM Citrix to check the machine out.
Last we have SM2 that has been MIA since June of this year. Has anyone been able to get in touch with redoulent about why he hasn't had it up and folding? Red used to be one of our most steady hosts, but he is also one of the original hosts that refused to sign a contract too, after the first few machines were stolen. :shakehead I hope that nothing bad has happened to him, but I would hate to think he's turned into a frigging thief also.
Now, to the active machines, it looks to me like some of them are performing below their potential. After all, if you are going to foot the electric bill to keep it running, then why not maximize the points return for your bucks.
For AMD systems with the present work being sent out, set the machine up to do timeless wu's, which are all Tinker units now. Most of them are 239 pointers or 241 pointers and they give a good steady points return, much better on a Tbird or AXP processor than a regular Gromacs wu. I have both my remaining AXP machines configured this way and they return around 150-200 points/day/processor. This is with a NF7 rig at 2400 and a MP dually at 2133. Another plus is that the Tinker wu's are not ram or memory bandwidth intensive, which is great for older machines that have only 128 MB ram and/or SDRAM.
For P3 machines, Tinker work isn't the greatest choice. Setting it up to do regular Gromacs work is probably your best option, unless you have 512 MB ram onboard. Then you can try the -advmethods flag and hopefully grab some BigWU work.
For a P4 based machine, 512 MB ram and using the -advmethods flag with bigpackets=yes set in the config file. This will let the P4 grab QMD work, which requires 500 MB minimum ram. The point output difference is tremendous when a P4 can get QMD's. Just look at the points/day output of the P4 that Jon and Sally are hosting and then compare it to the one that dancer is hosting, which only has 256 MB ram. If you can get him another 256 MB stick of ram, that 1.6 P4 will be knocking on the heels of the fastest AMD systems the SMX project has running.
0
Comments
That being said...
SM2 - Redoulent
Well... we have tried, and I mean several of the staff have tried, to no avail. We have been ignored, blocked, and to my knowledge, he has not responded. If anyone has information about redoulent (i.e. real name), please IM one of the staff so we can try other means to get a hold of him.
Thanks for the update on Redoulent, QCH. That info might be hard to come by, since he originally got the rig when we were Team Icrontic before the hack. All the info we had from there is lost, unfortunately. Maybe one of the old time committee members who were around when SM2 was originally assigned still have his info. Although that has probably changed too. I never would have guessed that Red would turn into a lying thieving SOB that deserves to be hung by his nads with a rusty nail.
Yep, that's what I'm talking about, Gnome. They do great on my AXP machines, much better than a regular Gromacs and not too much slower even on the magic p147x series or the 600 point BigWu units, which are in such short supply.
Sounds like a good idea. At only 128mb, IC_11 can't handle the big WUs. How do I set it up to just grab Tinkers?
I'm not saying that he falls into the same boat as some of the other guys that flat out told us "F*#& off, It's mine and you're not getting it back." but he is being abnormally hard to reach. No one on the staff has any info either. We've traced him down to a few other forums but he's not responding to us there either. IMing him doesn't work either... we are about out of ideas.
somthing is not right with that! who has this bad boy?
If you look at it's production log the reason the average is so low is because it's up for a week, down for a week, etc.
-drasnor
Motherboard: MSI KT3 Ultra2
Processor: AMD Athlon XP 1900+
Heatsink: Generic Socket A
Ram: Infineon 512MB PC2100
Hard Drive(s): Fujitsu 4.1GB
Video Card: ATI Technologies, Inc. 3D RAGE PRO AGP 2X
Network Card: Linksys LNE100TX (v4) Fast Ethernet Adapter
Case: Rosewill R103A
Power Supply: Generic 350W
CD/DVD Rom: NEC CDR-3000a 32x
Fans & Cooling: Generic 80MM (2)
We just put in a new hard drive because the old one literally ran out of space after some big work units (we were cutting it a little close anyway with 2.1GB). The memory checks out okay on memtest so the problem isn't there.
-drasnor
Processor: AMD Athlon XP 1900+
That is a pretty old CPU... maybe they could update you out fo the new Proc pile.....
But how is the coputer running in general. if you turn off Folding what is it running at? how is the ram..maybe some memory leakage is going on...
-drasnor
Hey Sledge, if you've got a box of 1900+s laying around, I'm sure we could make good use of them (if anybody mentions spare parts around me, they better be prepared for me to try to assimilate them )
If you’re wondering why I have all this. My old friend owns a cop repair store and ought recycled comps. Well when he went out of business he had about 280 comps that were going to be chucked. I gave him a couple hundy bucks and took every cpu, memory chip, CD drive Video Card and PSU I could get my hands on. I used and sold allot of the items and made good use of it all but I still have that box of CPU's somewhere
I just had a thought about trying to build a serial port watchdog; set up a cron job that generates serial port activity every hour resetting a solid state timer or purging a microcontroller register. If the timer reaches some voltage or counter value the circuit closes the reset switch. Doing it with a microcontroller wouldn't be so bad but my basic stamp is a bit on the large side and my HC05's require support circuits (clock generator et al) and except for one EPROM are all OTP. Solid state would be a lot cheaper but it would almost certainly involve some sort of RC timing circuit and the capacitor would have to be fully discharged after the machine pops off to prevent going into a reset cycle.
Ideas?
-drasnor
Now that we're somewhat settled since the move in April, I hope to get the real SM10 out of the box and get it folding again. I've had 3 comps folding in its place until I can get it set up. The PPD average for SM10 will go way down when it's back to fending for itself.
Yeah, I suppose it'd only overclock another 66-100 mhz or so then. 1720mhz is the highest I've ever had a Palomino stable, and then they're pretty sensitive to temperature. 1650 is a safe spot for the Palomino in IC_11 (which is unlocked). Another 50mhz or so isn't worth stability issues.
When we built SM27, it came with 2x256M sticks. However after Stanford changed the minimum ram for QMD's to 1 Gig, Sally added another 2x256M sticks she had stashed away.
SM27 has been running with 4x256MB since, working it's butt off.
I'm still waiting for IC7 to be delivered. I guess it's in the post somewhere. I have a nice new case and PSU all waiting.
overclocking: I seem to remember for folding that it's better to increase the multiplyer rather than trying to get the frequency up? This is not the best form of overclocking for general work but good for folding?
Advice please.
Cheers
Crypto
You should be able to do it with a PIC. They have an internal R-C oscillator that you can use if you don't want to hook up some sort of crystal for generating the clock. You can use one of the (16-bit) timers to count up. When it recieves a signal from the serial port, you can reset the timer. If the timer ever wraps from (2^16 - 1) to zero, you could have it toggle a relay or something. PICs are very cheap, as well. The only disadvantage is that you'll have to have a circuit to convert from serial voltage levels to 0-5v levels. Not too hard though.
Can't wait
-drasnor
Thanks for that info Mud, to be honest, that's somewhat of a relief!
Overclocking my existing rig was fraught with problems, and overall, I'm not convinced that the small gains made paid for the downtime due to the frequent crashes.
I guess I'm not too adventurous, steady as you go is my motto.
I'll be a steady contributor to the cause, I won't let you folks down.
Cheers
Crypto
-drasnor
On the other hand, SM25 is getting more and more unstable. It won't even stay up for a day now. Short of pulling it apart and testing each part individually I don't know what I can do for it.
-drasnor