Only half (50%) elapsed time registered
log in |
Message boards : Number crunching : Only half (50%) elapsed time registered
Previous · 1 · 2 · 3 · Next
Author | Message |
---|---|
THINGS STILL HAVE NOT CHANGED ON THE PC VERSION EITHER. | |
ID: 5332 · Rating: 0 · rate: / Reply Quote | |
Getting full hours here. Currently with 860 GCC hours in past 24 hours. That is 35.8 clients and I have 37 running. GCC doesn't always send another task right away and some get download errors. Plus 2 are tablets. So pretty dang close to being spot on. | |
ID: 5333 · Rating: 0 · rate: / Reply Quote | |
Getting full hours here. Currently with 860 GCC hours in past 24 hours. That is 35.8 clients and I have 37 running. GCC doesn't always send another task right away and some get download errors. Plus 2 are tablets. So pretty dang close to being spot on. It has nothing to do with GCC. On my Raspberry Pi I noticed I wasn't getting full hours when only running the QCN projects and WUProp (I was getting 24/7 hours a day for each application). I decided to run GCC as well and the figures for hrs/day got still even lower: 24/11. ____________ | |
ID: 5334 · Rating: 0 · rate: / Reply Quote | |
Getting full hours here. Currently with 860 GCC hours in past 24 hours. That is 35.8 clients and I have 37 running. GCC doesn't always send another task right away and some get download errors. Plus 2 are tablets. So pretty dang close to being spot on. GCC is a way to measure hours since GCC runs on every client. I do not have all other NCI apps running on all my clients. If I was getting partial hours from a client it would be applied to ALL apps running including GCC. | |
ID: 5335 · Rating: 0 · rate: / Reply Quote | |
THINGS STILL HAVE NOT CHANGED ON THE PC VERSION EITHER. I spend a hundred euros every month for this project. Why should I go on? You are always complaining that hours are not counted or that an application is not added quickly enough. If you are not happy, leave this project and create yours. But before you complain, you should check why your machine (4 cores) runs simultaneously a multithreaded workunit (4 cores) and 3 cpu workunits. ____________ | |
ID: 5342 · Rating: 0 · rate: / Reply Quote | |
lol ... give um hell Wild man ... ;) | |
ID: 5344 · Rating: 0 · rate: / Reply Quote | |
But before you complain, you should check why your machine (4 cores) runs simultaneously a multithreaded workunit (4 cores) and 3 cpu workunits. IT DOES NOT! Could it possibly be a problem with how BOINC and/or your project counts CPU's on real + virtual "VBOX" or Multi-Thread/Core when one or more NCI Apps are running at the same time? From what I can see the problems show up ONLY on my Multi-Core/Multi-Thread PC's but have yet to see it on my old single thread/core PC. Based on the Stderr output messages from each run that we can see on our results page, it appears the problems ONLY arise when ANY of the Multi-Core/Multi-Thread PC's runs a Multi-Core/Thread VBOX project* or when a Multi-Core/Thread CPU projects** AND 4 NCI Grid computing center Monkeys are running simultaneously with either of those. Below are TWO DIFFERENT examples from Computer 89002 (4 Core/Thread CPU) --- Task 72579597 Ran ONE or MORE Multi-Core/Thread app or a Multi-Core/Thread VBOX app + 4 NCI Monkey apps during the 6 hour WuProp also ran: Stderr output Task 61636560 Ran NO Multi-Core/Thread app or NO Multi-Core/Thread VBOX app + 4 NCI Monkey apps during the 6 hour WuProp also ran: Stderr output NOTES: * Multi-Core/Thread VBOX projects I currently or have recently run: LHC@home / CMS Simulation duchamp / Duchamp Sourcefinder Cosmology@Home / camb_boinc2docker (beta test) Cosmology@Home / CAMB ** Multi-Core/Thread CPU projects projects I currently or have recently run: XANSONS for COD / XaNSoNS BOINC for CPU (multi-threaded) yafu / YAFU for small composites Amicable Numbers / Amicable Numbers up to 2^64 Milkyway@Home / MilkyWay@Home N-Body Simulation I welcome other users that have complained here about the reduction in hours to also verify my findings. ____________ | |
ID: 5345 · Rating: 0 · rate: / Reply Quote | |
From what I can tell WUProp only counts the elapsed time, not CPU time. One can run 2 clients on the same computer and get 48 hours per day per CPU thread. | |
ID: 5346 · Rating: 0 · rate: / Reply Quote | |
You didn't lost any hours. There is a problem with activity host page. | |
ID: 5347 · Rating: 0 · rate: / Reply Quote | |
I am not buying into this argument, but I am going to say thank you Sebastien for keeping this project running and your downtime to almost zero. | |
ID: 5348 · Rating: 0 · rate: / Reply Quote | |
From what I can tell WUProp only counts the elapsed time, not CPU time. One can run 2 clients on the same computer and get 48 hours per day per CPU thread. Not complaining here but this just isn't true, at least not on my Double Client PC's. I still think I'm only getting Hr's Credited according to how much CPU Usage each Core is using. Maybe it's different for others but this is what I see when I check the Hr's for a turned in WuProp Wu. | |
ID: 5349 · Rating: 0 · rate: / Reply Quote | |
From what I can tell WUProp only counts the elapsed time, not CPU time. One can run 2 clients on the same computer and get 48 hours per day per CPU thread. It is true. I am running 2 clients doing CPU work on my 2P 2670v1s and I currently have over 1300 CPU hours in the past day on 32 threads, not including NCI hours. Xansons is set to single thread. A full 32 threads in one day is 768 hours. http://wuprop.boinc-af.org/activity.py?hostid=131071&preselect=day Asteroids@home Period Search Application 514,18 (58,10%) http://wuprop.boinc-af.org/activity.py?hostid=122461&preselect=day Asteroids@home Period Search Application 566,72 (73,99%) | |
ID: 5350 · Rating: 0 · rate: / Reply Quote | |
I said in my previous Post Maybe it's different for others but this is what I see when I check the Hr's for a turned in WuProp Wu. I don't know how it works, I'm running 4 Core 3700 CPU in HT Mode & with Dual Clients, could be the way the Clients are set up, maybe different than yours ? but I see nothing close to getting a full 24 Hr's off of each core. 16x24 would be 384 Hr's x the 19 Clients I have running now would be 6156 Hr's Per day not counting NCI or GPU Hr's. I'm usually lucky to see about 4000 Hr's per day, the usual 66% I've always seen, no where's near the 100% you say you get ... | |
ID: 5351 · Rating: 0 · rate: / Reply Quote | |
SSD vs hard drive might make a difference here, as might chipset, cache, GPU usage, OS, Boinc versions, VM's, MT, setup... | |
ID: 5354 · Rating: 0 · rate: / Reply Quote | |
I said in my previous Post You say you don't know how it works then deny it works when I show proof. Maybe it's just your setup. Getting 4k hours shows it is at least possible by your own numbers. Maybe it's just mt apps that screw it up. Just don't deny it and say it's not true at all. I would make sure to have all the WUProp app_config files setup with the correct gui_rpc_port. | |
ID: 5355 · Rating: 0 · rate: / Reply Quote | |
Yeah I'm just lying about the whole thing just because it's Sunday & I'm bored ... | |
ID: 5356 · Rating: 0 · rate: / Reply Quote | |
I said in my previous Post I counted 20 active clients, so 20 clients x 8 cores x 24 hours = 3840 hours. Last 24 hours, you get 3836.62 hours from CPU applications. You lost only 0.08% ____________ | |
ID: 5360 · Rating: 0 · rate: / Reply Quote | |
I said in my previous Post If I run 1 Project for 6 Hr's (Length that a WuProp Wu Runs) on 8 Cores I should get 48 Hr's Credit by my figuring, correct me if I'm wrong. Many times when I check a few Min's after a WuProp Wu is turned in running 1 Project for the last 6 Hr's all I see is 24-30 Hr's in gained Hr's for that Project. I don't check ever Wu turned in for the Hr's gained but I've see the only 24-30 Hr's gained enough times to make me think that's all I get on them all. Again I'm not complaining just trying to explain what I see, I like the Project & this Project is the only real reason I keep running or interested in BOINC so keep up the good work ... | |
ID: 5361 · Rating: 0 · rate: / Reply Quote | |
If I run 1 Project for 6 Hr's (Length that a WuProp Wu Runs) on 8 Cores I should get 48 Hr's Credit by my figuring, correct me if I'm wrong. That's what I expect too. What was running during that time? You've got all your stuff hidden. Have you gone back through your most recent set of tasks to see if the factorization comment is in the results of any client? Or checked the last day's activity for each client to see which one is missing hours? After I had setup my extra clients I had missed a couple of the app_config edits to use the correct gui_rpc_port and ended up missing hours. | |
ID: 5362 · Rating: 0 · rate: / Reply Quote | |
I had missed a couple of the app_config edits to use the correct gui_rpc_port and ended up missing hours. If I didn't have the correct qui rpc port I wouldn't think I would even get any Wu's to the client ??? | |
ID: 5363 · Rating: 0 · rate: / Reply Quote | |
Message boards :
Number crunching :
Only half (50%) elapsed time registered