Forum > Linux
SETI MB CUDA for Linux
riofl:
--- Quote from: sunu on 17 Aug 2009, 07:32:43 am ---riofl, give me a link to your host.
Compiled boinc gave me also increased benchmarks. Don't have any real importance though.
--- End quote ---
ok so then it doesnt mean anything about my ram change... hope this is the right link. i took it from the details link from my computer listings page
http://setiathome.berkeley.edu/show_host_detail.php?hostid=4166601
sunu:
riofl, I'm sure you know, your tesla card has some problems. It gives errors in some workunits. If you look in your errors page, all those workunits were run by the tesla card. It does run successfully though in other workunits.
Checking the reported run times, I don't see any significant difference between eg 18 August and 14 August when you were running 6.6.11.
I do see though that most of the workunits were restarted 2 or 3 or more times. The initialization phase of a cuda task takes about 30 sec. If it is restarted 2 times you lose 1 min and with a total computation time of eg. 14 min you lose 7% credit right there.
You've said that you run the rebranding script several times per hour, why? I search for vlars once per day, sometimes once per two days, and that is more than enough. If newly downloaded tasks get crunched only a few hours later, increase your cache so they are crunched after 2-3 or more days so running the script once per day will be enough.
riofl:
--- Quote from: sunu on 18 Aug 2009, 12:04:40 pm ---riofl, I'm sure you know, your tesla card has some problems. It gives errors in some workunits. If you look in your errors page, all those workunits were run by the tesla card. It does run successfully though in other workunits.
Checking the reported run times, I don't see any significant difference between eg 18 August and 14 August when you were running 6.6.11.
I do see though that most of the workunits were restarted 2 or 3 or more times. The initialization phase of a cuda task takes about 30 sec. If it is restarted 2 times you lose 1 min and with a total computation time of eg. 14 min you lose 7% credit right there.
You've said that you run the rebranding script several times per hour, why? I search for vlars once per day, sometimes once per two days, and that is more than enough. If newly downloaded tasks get crunched only a few hours later, increase your cache so they are crunched after 2-3 or more days so running the script once per day will be enough.
--- End quote ---
yes i am going to retire the tesla short.y but first im going to try to replace the existing incorrect thermal pads on all the chips. if that doesnt fix it i will ship it back to my boss who sent it to me in the first place and let him use it on a windows setup. i will then run just the single gtx285 for a month or 2 and then get another gtx285 to replace the tesla. the 285 is considerably faster than the tesla anyway. (127gflops vs 74gflops by boinc measurements)
the reason i picked every 20 min was i noticed a number of computation error results when i ran it just once an hour. i suppose the easiest way to keep it from downloading all the time is to set the cache to 10 days, get it all then run the script then turn it back to 2 days or something so it wont download more. when i ran the cpugpureport script several times i found that it showed vlar/vhar assigned to gpu sometimes several times in an hour meaning it got more workunits. a second reason for doing this is the tesla locks up sometimes as much as every hour and a restart of boinc cures it.
maybe ill just ignore all that and run the script once every few hours using a large cache so it wont get more without me making it do so. that way i can keep control of it rejecting vlars.
thanks for checking. i didnt think frequent usage of the script would cause that much of a change.
riofl:
ok i changed my cache from 6 days to 10 but no workunits.. prob cause the project is in maintenance. script is set to run every 4 hrs until it gets its cache then ill change that to once a day and set the cache back to 2 days.
lets see what that does
sunu:
Why play with your cache levels? Change from 6 to 10 and then back to 2, why? Pick a cache level and leave it there. I'm using 10 days. If you were using 6 days, it is fine also. 6 days cache means that the workunits downloaded now will be crunched in about 6 days, so you have 6 days to check for vlars. No need to run that script x times per hour or x times per day.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version