Switched to Einstine |
![]() |
| log in |
Message boards : Number crunching : Switched to Einstine
1 · 2 · Next
| Author | Message |
|---|---|
|
Ok, been putting up with this B---S---t for too long, I have been with SETI for years and although I understand that computers and programming have issues at times my computers are not gettng any work and I have to do the NNT all the time to send work (only GPU units, nothing else) | |
| ID: 1307638 · | |
Ok, been putting up with this B---S---t for too long, I have been with SETI for years and although I understand that computers and programming have issues at times my computers are not gettng any work and I have to do the NNT all the time to send work (only GPU units, nothing else) Thank you. Your switch to Einstein has help alleviate the problem. In case you didn't know the problem is to many crunchers with too many fast crunch cards. Every user that switches makes the problem a little less. ____________ | |
| ID: 1307724 · | |
|
Hi Jim, | |
| ID: 1307727 · | |
|
I can't say I am happy with the current state of things here on my favorite project, but I do know that they shall get better. After all, with over 13 years under my belt here, I have seen a lot of ups and downs. | |
| ID: 1307733 · | |
I can't say I am happy with the current state of things here on my favorite project, but I do know that they shall get better. After all, with over 13 years under my belt here, I have seen a lot of ups and downs. Helps is on its way, the simple trick. Make the workunits a lot longer to process, by a factor of 4 or so. This will give us a year or so....... ____________ TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking. | |
| ID: 1307735 · | |
Ok, been putting up with this B---S---t for too long, I have been with SETI for years and although I understand that computers and programming have issues at times my computers are not gettng any work and I have to do the NNT all the time to send work (only GPU units, nothing else) Same here. I run both. Since SETI is down, again, Einstein is running. ____________ | |
| ID: 1307738 · | |
I can't say I am happy with the current state of things here on my favorite project, but I do know that they shall get better. After all, with over 13 years under my belt here, I have seen a lot of ups and downs. Yes, I read that..... Another option, which Eric did not broach, might be to consider something more robust than the mysql database. This subject has been discussed once or twice in the past, and it was noted that we were starting to approach the limits of mysql. At least in this heavily burdened scenario. ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1307740 · | |
Thank you. Your switch to Einstein has help alleviate the problem. In case you didn't know the problem is to many crunchers with too many fast crunch cards. Every user that switches makes the problem a little less. You could count with my help with 7 hungry hosts. :( To avoid the dissease they are killing the patient... something cleary out off maind! discussed once or twice in the past, and it was noted that we were starting to approach the limits of mysql. If that was a "time bomb" well know problem, why dont´t make nothing to avoid before it´s exploding? Matt please, please... I beg you, return as soon as you can... ____________ | |
| ID: 1307742 · | |
|
It will be interesting to see how would Einstein handle load IF heavyweight crunchers like msattler and Juan decides to switch to Einstein with full capacity until Seti is back up. | |
| ID: 1307743 · | |
Thank you. Your switch to Einstein has help alleviate the problem. In case you didn't know the problem is to many crunchers with too many fast crunch cards. Every user that switches makes the problem a little less. I'll reiterate my previous advice. Set Einstein to zero workshare, and leave Seti as is. Your computers will automagically return to Seti when work is available. Follow the kitties, my friend. Follow the kitties. ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1307747 · | |
It will be interesting to see how would Einstein handle load IF heavyweight crunchers like msattler and Juan decides to switch to Einstein with full capacity until Seti is back up. As you could notice, I all ready switch to Einstein (0 resource for now) and i know Mark and Tbret do the same, we 3 alone have more than 1.2 MM in SETI RAC, so by doing that we will help to fix the SETI problem... Firehawk allready switch to GPUGrid, TPL to collantz, Hope Russ do something like that soon (don´t have any ideia to what project for now)... Janice/Steve ithink going to Einstein to, anyone else not shure... At least a combinned force of more than 2.5MM in SETI RAC. But be clear to all, i´m not happy to do that. The way the things takes, everyone will think we are the source of the problem, exactly the oposite, we just trying to follow a dream (Help to find an ET) and do our best for the project... nobody tell us "you can´t put to many crunchers to work or the project will be down..." (edit) Follow the kitties, my friend. Follow the kitties. I all ready do that, allways follow the kitties path... You know, I´m a kitties fan! :) I´m going to put 2 new 690 to crunch today... so count with some more help from my side... Hope Einstein could welcome us without cause any problem to them, thats not my ideia, just want to contribute with science and Try to help to find a ET... snif! ____________ | |
| ID: 1307749 · | |
|
A little factlet for consideration | |
| ID: 1307752 · | |
172 CPU's, mostly i7's and i5's Makes Me think : I have alot of work to do if I plan on surpassing them. mwuahahaha! | |
| ID: 1307824 · | |
172 CPU's, mostly i7's and i5's Me thinks you better be making a lot of money. The electricity bill alone with that many computers would kill most. ____________ | |
| ID: 1307835 · | |
I'll reiterate my previous advice. Einstein tends to eat up a lot more disk space and setting Einstein to 0 workshare will control the number of work units requested. I had hundreds of systems almost run out of diskspace the last time SETI had a prolonged outage and all my machines started trying to keep 10 day caches of Einstein work units. Follow the kitties advice and all will be right with the world.... ____________ | |
| ID: 1307842 · | |
172 CPU's, mostly i7's and i5's If you look at the top 20 participants the combined RAC is a lot higher. Totaling about 7,353,253. However that is only 4.7% of the total SETI@Home RAC. BOINCstats shows 268,760 active users for BOINC combined & 151,581 active users for SETI@Home. Einstein by comparison only has 36,829 active users. I can imagine that if any of the other projects has a sudden influx of 100,000 users their systems would show similar strain. ____________ SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today! | |
| ID: 1307844 · | |
I'll reiterate my previous advice. It's their CPU application (S6LV1) which tends to eat up disk space: there are enough other CPU projects out there that we can probably spread the load more widely if this current outage turns out to be prolonged. S6LV1 is also approaching a transition point (45 days work remaining, less if we all rush over there and gobble it up) - things tend to get a bit spotty there with large downloads as they fill in the final gaps. I suspect that more people here will go to Einstein to run their CUDA apps. They don't hog disk space the way their CPU apps do, but you need a robust ISP and a generous data allowance - my GTX 670 is downloading about 60MB an hour (two tasks at a time, about 30 minutes runtime) when crunching Einstein. And that can lead to a significant gap between jobs (as one set of files uploads, and the next set downloads) when running Resource Share zero. | |
| ID: 1307849 · | |
|
As allways, Richard is right. | |
| ID: 1307859 · | |
It's their CPU application (S6LV1) which tends to eat up disk space: there are enough other CPU projects out there that we can probably spread the load more widely if this current outage turns out to be prolonged. S6LV1 is also approaching a transition point (45 days work remaining, less if we all rush over there and gobble it up) - things tend to get a bit spotty there with large downloads as they fill in the final gaps. Yes I only have 1 system that has a CUDA card in it. 99.9999... percent of the work I have done was CPU only. I have resigned myself to crunch on what the large GPU systems leave behind. I do what I can with what I have access to. Still not a bad RAC considering. ____________ | |
| ID: 1307862 · | |
my GTX 670 is downloading about 60MB an hour (two tasks at a time, about 30 minutes runtime) when crunching Einstein. And that can lead to a significant gap between jobs (as one set of files uploads, and the next set downloads) when running Resource Share zero. You can trick BOINC to cache an additional WU if you set <count> to 0.99 (if running 1 WU at a time) and probably 0.49 if running 2 at a time. Probably because the second one I haven't tested, 0.99 works for me with Collatz as backup project for Milkyway perfectly. I'm running 2 Milkyway WUs at once, when the first (of the last two) is finished, the first Collatz WU is cached, but not started, when the second MW WU is finished BOINC starts the Collatz WU and requests a second one since it thinks that the GPU is not completely in use. But once it has it, it won't start it, because that would be more than 1.00. Once the first Collatz WU ist finished, BOINC starts the next one, uploads the result and requests next WU. So I always have one waiting to start. With <count> 1.00 for Collatz I had always a break of about 15 seconds (every 20 minutes or so), because BOINC would first upload the result, than report and request new WU and finally download the new WU. That was not good enough for me. Unfortunately this does not work for CPUs, BOINC would start both WUs. ____________ . | |
| ID: 1307888 · | |
Message boards : Number crunching : Switched to Einstine
| Copyright © 2013 University of California |