right click on the job to upload itself... and select 'retry now'Originally Posted by jlangner
that should do it.
Let me know if you have any problems.
Chuck
Senior Member
right click on the job to upload itself... and select 'retry now'
that should do it.
Let me know if you have any problems.
Chuck
Senior Member
PS: Don't forget to force the update afterwards.... saves time in getting credits and reduces risk of having timed out.right click on the job to upload itself... and select 'retry now'
that should do it.
Let me know if you have any problems.
Chuck
Senior Member
Jeff... thanks... I have CNQ as well... am not overclocking at all... pure stock now. I am back at full 12x and 200 mhz, 64 bit + dual channel (quad total capable) and stable at 53C CPU, 40C MB.
I did a COMPLETE rewiring of the chassis and improved airflow. It's much cleaner now... when I idle the cpu, the temp falls like a rock... so I think things are going well. I have one more T-take fan to install tomorrow. That will be when I give this a temperature break. I have to give it a temperature break soon... The AS-5 needs that.
I'm trying to help out as much as possible since, getting us up as far as possible with 'pending credits' because Chaz lost a major machine, I will be down for about 2-3 hours, and my 3200+ isn't back up yet.
Chuck
Senior Member
Attention all Predictor participants... PLEASE UPGRADE TO 3.20 ASAP.
See below please.
Per the 'current progress' link on the predictor site reads....
7/16/04 - Updates for today:
The scheduler on the server has submitted a lot of work to Mac hosts and is now waiting for more Mac's to provide duplicate wu's for validation purposes (remember we are using Homogeneous Redundancy which means that wu's are only send out to similar hosts because the calculated results are different on different CPU's/OS's). In case you are wondering why so much work has been submitted to Mac's if there are not so many around, you are right; we do so too and have mentioned this to the boinc-development team as a problem (we'll start thinking about this ourselves too ofcourse).
Michela has finished work on the Linux version of the Charmm application and we'll release it on the grid today. We'll only generate a small number of wu's for now though since we like to find out how and if results for this platform are coming back correctly. We have implemented some minor bugfixes and improvements in the Mfold version for Linux as well. Both science applications will be upgraded to version 3.10.
The Mfold and Charm applications for Windows have also been optimized a bit more and some minor bugfixes have been made: Charmm shouldn't crash anymore at the start of a new workunit, because a test is now made if files are already in the slot directories and Mfold provides us with some useful information and an error code in case something goes wrong. Their respective versions will be upgraded to 3.10 as well.
We are trying to optimize a lot of queries in the server code since we (like the seti project) are starting to notice some performance problems on the server now that we are getting more and more users (more than 4000) and computers (more than 10,000!). The boinc development team is working on this as well and will soon come out with a new version 4 of the boinc software where they have addressed a lot of performance questions.
Everybody should update to version 3.20 of the boinc core client (CC) as soon as possible. This will fix a lot of problems we currently have with results returning with cpu time 0 (and accordingly 0 credits are granted if this is the first result in a set). It will also make the benchmark numbers based on the same algorithms for all hosts; this also will solve some problems with credit allocation. Actually, in a couple of days we will set the minimum version required to 3.20. People who have not upgraded yet will not get any work anymore that way. Thanks!
(personal comment)
** I asked for the 3.20 minimum..... We beat intels and they should NOT be getting more credits than us! Time to play fair! ****
Also, there will be a new FAQ coming up for Predictor shortly.... Anyone with emails can email me directly or PM me and I will put ANYTHING you have in the FAQ, since that's my primary contribution.
Please feel free to PM me references to recent issues we've solved, or personal experiences you've solved on your own... it's all valuable materal.
Last but by FAR least, Thank you all.. We've made a *BIG* impact on Predictor and are helping a good cause as well as making some HUGE strides in standings.... Anyone who's bored elsewhere or has cycles to burn is welcome to join.
Chuck
Senior Member
Same as last 6 days:
"Predictor@home - 2004-07-17 02:33:58 - Temporarily failed upload of t0212C_1_3121_1_0
Predictor@home - 2004-07-17 02:33:58 - Backing off 33 minutes and 8 seconds on transfer of file t0212C_1_3121_1_0"
How do i delete it. It is stuck!
Senior Member
First check... but i assume that Boinc is running and other jobs are fine, right? (Upload and download?)
Then, please check the web page and see if it has that stuck WU is marked as timed out (no reply) or with some other error... The easiest way to find it is go to your computers list from your 'User Page', then look down through the list for that WU number....
If expired or 'client error' or whatever it will have to come out. If not, hammer it again and again (6 times max, 1 per minute) until you get an error in the status on the web page.
If Removal required....To do this by hand is easy, just get it all in 1 shot.
1) Shut down BOINC/Predictor and edit the client.xml file (in the top level predictor directory) to remove that job from the list.....(Edit using an editor that supports LONG lines and formatting... like Wordpad in Windows). You will find that there are multiple files which comprise that WU, you must get them all. Just watch the XML tags (like HTML tags), deleting each file element from start tag to 'slashed' end tag.
2) You must write down the WU name and # and then go to your predictor\projects\-url- folder and remove (delete) all components of the WU. Most likely, you will find just the .res file (result).
3) Once all are gone, you may restart predictor and it will be gone.
I *ASSUME* you did not move the job from one CPU to another, did you?
If so, it will never upload.
Also, If this was a job running at time of a crash, you must wait until ALL jobs are gone from your run queue (disable network access is the easiest) and the 'slots' folder(s) should be empty.
Make sense?
Chuck
Senior Member
I am working on the FAQ and forgot to tell you all about this little, non-obvious tweak to predictor performance.
Mfold writes a checkpoint to disk at that 'write to disk' interval in your general profile. The jobs we are running generate about a 50MB file.
You must decide whether it's safer and quicker to recover and run overall by writing out the checkpoint file more frequently (e.g. 30-60 seconds) -or- hold it in memory longer (which I do... 180 seconds).
In the case of Charmms jobs... you may never write the file at all! LOL
The impact this has is simple... if you crash... the job will recover from the last checkpoint. SO, which is better for your PC? more frequent disk writes of 50MB or to simply recompute those extra couple minutes?
Chuck
Member
Moved 2700XP from D2OL to Predictor. Pretty much have my max effort on Predictor now.I'm trying to help out as much as possible since, getting us up as far as possible with 'pending credits' because Chaz lost a major machine, I will be down for about 2-3 hours, and my 3200+ isn't back up yet.
Senior Member
ITS ALIVE !!!!!
Had to steal ram from another machine to make a large enough ramdisk. It didnt benchmark for crap, but at least it'll run until new HDD shows up.
Senior Member
Well I killed that one. Edited file wrong or something. :twisted: :evil: Oh well, lost 3 results.
Posting Permissions
Reply With Quote