Posts by mikey
|
61)
(Message 4562)
Posted 10 Jul 2015 by 
mikey
Post: Thanks for answering. Yes it is running Android. The only project that sends it WU's at the moment is Collatz. So, if they can manage it why can't other projects? Each project has to have their own programmer to write their app, few actually share, probably for secrecy reasons. This means that the project must know someone who can do it and will do it for free, or nearly free, as there is not alot of money at most projects. Asteroids is mostly a one man show, he does have some friends that help him out, but he is mostly THE guy. Collatz tends to be a proof of concept project for stuff, it is usually on the bleeding edge of new stuff before it gets rolled out to the other projects as they chose to do it or not. |
|
62)
(Message 4533)
Posted 21 Jun 2015 by
mikey
Post: I noticed on my Intel Core i5-2520M that the WUs are running about 3 hours. I'm wondering if the long WUs on Android are due to (lack of) optimizations? I'm running a test to see if they are still running that long... Each project uses its own programmers, most do not share them, so yes it's quite possible it is not fully optimized. Multiple programmers can mean paying multiple people and most programmers tend to be really good at one platform and okay at the others, if they even do them. |
|
63)
(Message 4532)
Posted 21 Jun 2015 by
mikey
Post: I've upgraded Then it's probably not you, if the error rate is too high there are other fish in the sea. Most projects have errors, none are perfect 100% of the time, some have upto 15% errors as they work on the apps. On you XP machine you have 25 errors and 62 valid units, BUT 99% of the errors were caused by the project, not you! On the Win7 machine you have 1047 valid units and only a total of 17 problem units, with again some of those being project related. Are you using the gpu to crunch at another project? If so are you leaving at least one cpu core free just to feed the gpu? |
|
64)
(Message 4524)
Posted 19 Jun 2015 by
mikey
Post: Hi, could you pls manage that only 80-90% of the GPU is used like GPUGRID does? I can´t watch YT when 100% is used :( Each project is different, some people want the near 100% usage, others like you want it a bit less. Boinc is designed to run when you aren't using the pc, you are not running it that way, neither are most people btw. |
|
65)
(Message 4517)
Posted 18 Jun 2015 by
mikey
Post: My Asteroids account shows a total of 1379 work units, of which there are 811 valid ones, 11 invalid and 548 errors. MOST of your errors are 'download errors' and that has been an ongoing problem here and there is nothing you can do about it. Some of your other errors could be because you are using an older version of Boinc and not the latest 'release version' of 7.4.42. You are using version 7.4.27, there have been some changes, but I am not positive they are affecting your results, but to be safe upgrade and see if some of the errors go away. |
|
66)
(Message 4511)
Posted 15 Jun 2015 by
mikey
Post: You missed my point. Was asking why this happens: I believe every workunit is EXACTLY the same, a workunit is a workunit until a pc asks for some, then depending on what it asks for the ones they get are labeled as such for security purposes. So if your cpu asks for units you get units labeled for your cpu, but the exact same unit could have been labeled for an opencl or cuda gpu instead if that request came in first. So 'it's normal' what you are seeing. |
|
67)
(Message 4506)
Posted 12 Jun 2015 by
mikey
Post: I have noticed that additionaly to the standart WUs there are some taking only half the time of normal ones. When looking at the tasks iv seen that the short ones get done considerable faster on a CPU. I believe all the units are the same here, meaning there aren't any short or long units. Your gpu is very fast and very new, that could be alot of why it seems 'wasted here' doing the workunits. Alot of us have much older gpu's and the project needs to support us too, as we are there bread and butter. All projects deal with how to cut off old hardware, and/or make new units that better support the capabilities of the newer and much faster hardware. Projects appreciate your hardware as it just flies thru the units, whereas mine tended to be alot slower. |
|
68)
(Message 4497)
Posted 7 Jun 2015 by
mikey
Post: Can you help me to understand something more about this? Sorry With all the testing/changing/etc that I have done, I have one machine limited to seti only (4 processors), one running both seti and asteroids (4 processors) and one dedicated to BU only. DAILY but it must be considerable since the other machine refuses to share, and I don't have the patience to wait it out and see if it would eventually stabilize. I did wait a full week and that machine only ran asteroids units the entire time. It had a seti unit that it put on hold (waiting to run) that just sat there until I stopped asteroids again on that machine. Boinc was never designed to be run 24/7 at 100% of the cpu usage in a pc, it was designed to use SPARE cpu clock time, NOT be the primary program running on a pc. Therefore it doesn't act like we want it too all the time. And no Dr A isn't going to change that anytime soon, he is still trying to get grant monies based on his original model as I described it. Notice both averages are climbing and that the spread between the averages is still growing even with only one core running asteroids and 7 running seti. That by itself makes it clear that credits have no bearing on how boinc figures resource share. Again DAILY average credits, not anything the stats sites come up with. As for one cpu core running Asteroids and 3 running Seti, that is just a right now thing, it will change again. Percentages is NOT related to cpu core usage. As I think I said before as you are doing with your BU machine, the best thing is to put each project on its own machine, that way each can run at the 100 percent with no interference from the other projects. That's how people like me end up with 15 pc's in our home running Boinc. |
|
69)
(Message 4491)
Posted 3 Jun 2015 by
mikey
Post: sorry I clicked post twice |
|
70)
(Message 4490)
Posted 3 Jun 2015 by
mikey
Post: Can you help me to understand something more about this? Is BU running on the cpu too? All of this on the same machine? That could be the problem. I too run BU but only use miners, but still need to keep a cpu core free just to feed them, just like I do for the gpu's I have. When I look at your average credit it says Seti is at 5162, BU is at 5147 and Asteroids is at 2670, are you running them all on the same machine? If so your 75% and 25% numbers are being skewed by BU. |
|
71)
(Message 4473)
Posted 29 May 2015 by
mikey
Post: An update on this, though still far from stabilized. There is just no way to make Boinc crunch some of both kinds of units all the time, it is trying to even out the Recent Daily Credits and with different deadlines, credits being awarded etc, etc what you are seeing is normal. Now why it's crunching 4 units on 3 cores I have no idea, unless you have Boinc setup to use all of your cpu cores and start the VM after Boinc is up and running. IF that's what you are doing trying changing Boinc to only use 3 of the 4 cpu cores, in the Boinc Manager, and then next time you reboot the pc only 3 units should run at a time, reserving the other core for your VM. |
|
72)
(Message 4469)
Posted 26 May 2015 by
mikey
Post: The reason your units are running at 'high priority' is because Boinc thinks if it doesn't run those units NOW they won't be finished prior to their deadline. One solution would be to reduce your cache settings to just one or two days, that way with projects having a seven day deadline you should never see the 'high priority' crunching again. My pc cache settings are 0.50 for the first box and 0.25 for the 2nd box, that way I have about a one day cache and never see the 'high priority' crunching takeover. That is a problem for alot of people, the lack of a good consistent connection, I am glad yours is not much better! Your comment about the deadlines seems to support what I had already surmised in that it was the likely cause of the problem. The size of my cache both earlier and now would seem to support that premise. However, I will have to process and reduce the current cache before I can really see what the usage balances out to. Will see what happens and let you know. You could abort some of the units if it is causing a huge problem, but just crunching thru them is best if you can. I am interested in the outcome of this. |
|
73)
(Message 4462)
Posted 25 May 2015 by
mikey
Post: I previously was running both Seti and Asteroids on my PC, and found that often Asteroids would take over the entire PC (4 processors) for days at a time while running work units at "high priority". My preferences were set to share work equally. I then stopped processing A@H work units because it was starving the S@H project. Boinc doesn't work like that! Boinc tries to accommodate your 25% setting, for example, not thru actual crunching but by monitoring your recent daily credits and letting one project crunch more until it reaches that 25% setting on a daily basis. Give your pc some time and it WILL work itself out, barring any lack of units being available at one project or another, over time. Lack of units will just make the time frame longer. The reason your units are running at 'high priority' is because Boinc thinks if it doesn't run those units NOW they won't be finished prior to their deadline. One solution would be to reduce your cache settings to just one or two days, that way with projects having a seven day deadline you should never see the 'high priority' crunching again. My pc cache settings are 0.50 for the first box and 0.25 for the 2nd box, that way I have about a one day cache and never see the 'high priority' crunching takeover. The varying deadlines at the different projects is a long standing problem in Boinc, one project has a 7 day deadline for it's units while another project has a 3 day deadline. Trying to manage multiple projects with widely varying deadlines on a single pc is why alot of us went to multiple pc's, that way we can run one project on each pc. Or we can put all of our pc's on one project and quickly crunch alot of units. What we want, but hasn't been made available as of yet, is the ability to crunch project A on X number of cpu cores and project B on some other cpu cores, with the cores being dormant if the project doesn't having any units. There are LOTS of other priorities right now, with the project percentage one being an ongoing work in progress. |
|
74)
(Message 4454)
Posted 18 May 2015 by
mikey
Post: My Samsung Tab 4 completed the last few with elapse times between 39-49 hrs. So your time doesn't seem too outlandish. You seem to have multiple accounts over time and pc's, when I look your name up in both Boincsats and FreeDC it comes up with multiple accounts for that name. Could they be accumulating on another account? http://stats.free-dc.org/stats.php?page=search&proj=&team=&name=DadX&exact=N&cross=N http://boincstats.com/en/stats/search/#DadX |
|
75)
(Message 4451)
Posted 16 May 2015 by
mikey
Post: What is the average time for these tasks on Android? Unless you find another user I don't have a clue how to find out. |
|
76)
(Message 4448)
Posted 15 May 2015 by
mikey
Post: Nbody v1.5 looping. 5 min. task Im aborting after 4+ hours running 8 processers. I7, Win 7, 12 GB Ram, 2 TB HD. This is Asteroids NOT MilkyWay, you might want to post your problems on the MW forums. |
|
77)
(Message 4437)
Posted 10 May 2015 by
mikey
Post: for whatever reason the charger - is responding to the crunching load ; ans is working Ok +1 |
|
78)
(Message 4432)
Posted 9 May 2015 by
mikey
Post: I just completed my first task for Asteroids @ home, but it took a whopping 59 hours. For Android, is that too long? It validated so not too long for the project, but it does show how inefficient the ARM processor can be. What else were you doing with it while it was crunching? Did you leave it plugged in the whole time? |
|
79)
(Message 4428)
Posted 6 May 2015 by
mikey
Post: Getting a lot of these recently I see you are still at Boinc version 7.4.36, why not try upgrading to BOINC 7.4.42 and see if that helps any. It has been the 'release version' for a while now. If you want to be ahead of the curve you can try 7.5.0 but it is still in the testing phase and could cause problem, although I haven't seen any of them so far in the month or so I have been using it on 2 of my pc's. You can get any Boinc version here http://boinc.berkeley.edu/dl/?C=M;O=D |
|
80)
(Message 4411)
Posted 22 Apr 2015 by
mikey
Post: It's not automatic. We have to prepare input files before so the script is automatic, but not it's starting. We have to run the script manually. Ahhh thanks for the clarification. Darn 6:30am and I already learned my one new thing for today, I guess the rest of the day will be boring. 
|
Previous 20 · Next 20