Posts by robsmith

21) Message boards : Android : BOINC & Android TV (Message 103626)
Posted 21 Mar 2021 by robsmith
Post:
OK, that's almost certainly the "wrong" temperature sensor being detected as the battery sensor. I think Jord's solution is about the only way to go as, sadly, I don't think every Android hardware system follows the correct use of sensors :-(
22) Message boards : Android : BOINC & Android TV (Message 103622)
Posted 21 Mar 2021 by robsmith
Post:
How long between starting the task and the message appearing?
23) Message boards : The Lounge : Grumbles, Glory and Covid-19 (2) (Message 103604)
Posted 19 Mar 2021 by robsmith
Post:
The returns process...........
24) Message boards : The Lounge : Grumbles, Glory and Covid-19 (2) (Message 103494)
Posted 12 Mar 2021 by robsmith
Post:
That explains why BT are having to replace miles of "copper" in some of the newer estates around here, while those of us in the outlying longer established estates just sit waiting and waiting and waiting......
(They are actually pulling in two cables at once, a "copper" one and a fibre one", however they are not automatically connecting houses to the fibre cables....)
25) Message boards : The Lounge : Grumbles, Glory and Covid-19 (2) (Message 103492)
Posted 12 Mar 2021 by robsmith
Post:
More dough - if they are doing fibre down your street it is nominally "free", but if they are laying fibre where no phone lines exist it's £££££££££££
26) Message boards : The Lounge : Grumbles, Glory and Covid-19 (2) (Message 103488)
Posted 11 Mar 2021 by robsmith
Post:
MP is not the case - I live just round the corner from mine.
It's BT's "resource planning", the town has a huge number of new houses being built and they get priority (in BT's eyes) over their long suffering customers.
27) Message boards : The Lounge : Grumbles, Glory and Covid-19 (2) (Message 103481)
Posted 10 Mar 2021 by robsmith
Post:
Much the same where I live, when I asked BT a few weeks ago "When will fibre come to this corner of town?" the answer was "At least two, probably three years".
I'm only a few miles from Birmingham, in an expanding town with a population heading toward 100k. Further pressed they admitted they were doing the new-builds before thinking about in-filling the rest......
As for where my brother lives, it's more like five years, but then he does enjoy the peace of living on the edge of one of the moors in the south west where cell phones only work when there are no leaves on the trees (I jest not!).
28) Message boards : Questions and problems : Problem with "max concurrent" in app config. (Message 103454)
Posted 7 Mar 2021 by robsmith
Post:
In general, 'target work buffer' is measured in wall time, and 'shortfall' is measured in core-time. If cache is empty, shortfall=ncpus*buffer.

Thanks Richard - I'm less confused than I was.

(PM on its way)
29) Message boards : Questions and problems : Problem with "max concurrent" in app config. (Message 103452)
Posted 7 Mar 2021 by robsmith
Post:
I just set Work_fetch_debug for a few minutes and, in the midst of thousands of lines I found this bit:
07/03/2021 19:52:30 | | [work_fetch] No project chosen for work fetch
07/03/2021 19:53:30 | | choose_project(): 1615146810.159882
07/03/2021 19:53:30 | | [work_fetch] ------- start work fetch state -------
07/03/2021 19:53:30 | | [work_fetch] target work buffer: 86400.00 + 864.00 sec
07/03/2021 19:53:30 | | [work_fetch] --- project states ---


My cache is set to 1 day, plus 0.01 days, and I'm running 4 cores.
One day is 86400 seconds, and thus 0.01 days is 864 seconds, with no correction for the number of cores in use.....
(Cancel one thought I had - I was expecting these figures to be multiplied by the number of cores in use.)

I've just forced a finished WCG task to report - and the first few lines are:
07/03/2021 20:02:46 | World Community Grid | update requested by user
07/03/2021 20:02:46 | | [work_fetch] Request work fetch: project updated by user
07/03/2021 20:02:50 | World Community Grid | [sched_op] sched RPC pending: Requested by user
07/03/2021 20:02:50 | World Community Grid | piggyback_work_request()
07/03/2021 20:02:50 | | [work_fetch] ------- start work fetch state -------
07/03/2021 20:02:50 | | [work_fetch] target work buffer: 86400.00 + 864.00 sec

Then a whole load of stuff relating to suspended and no new tasks projects.

Then, eventually:
07/03/2021 20:02:46 | World Community Grid | update requested by user
07/03/2021 20:02:46 | | [work_fetch] Request work fetch: project updated by user
07/03/2021 20:02:50 | World Community Grid | [sched_op] sched RPC pending: Requested by user
07/03/2021 20:02:50 | World Community Grid | piggyback_work_request()
07/03/2021 20:02:50 | | [work_fetch] ------- start work fetch state -------
07/03/2021 20:02:50 | | [work_fetch] target work buffer: 86400.00 + 864.00 sec


and still more stuff about projects that can't get tasks (as before)
07/03/2021 20:07:04 | World Community Grid | [work_fetch] share 1.000
07/03/2021 20:07:04 | | [work_fetch] --- state for NVIDIA GPU ---
07/03/2021 20:07:04 | | [work_fetch] shortfall 174528.00 nidle 2.00 saturated 0.00 busy 0.00


Which doesn't make sense to me, apart from being about double my buffer size.

It would be interesting to see what your system is saying & doing
(But as Richard said, only leave Work_fetch_debug set for a few minutes - it produces a frightening number of lines in very little time.
30) Message boards : Questions and problems : Problem with "max concurrent" in app config. (Message 103449)
Posted 7 Mar 2021 by robsmith
Post:
One thing that I see that could be giving you a bit of an issue are these two lines:
20756 Kryptos@Home 07-03-2021 02:54 PM You are attached to this project twice. Please remove projects named Kryptos@Home, then add http://www.kryptosathome.com/


&

21070 Kryptos@Home 07-03-2021 03:55 PM You are attached to this project twice. Please remove projects named Kryptos@Home, then add http://www.kryptosathome.com/


In the past (dark and distant) doing this gave me some strange work-fetch issues.....
31) Message boards : Questions and problems : Problem with "max concurrent" in app config. (Message 103446)
Posted 7 Mar 2021 by robsmith
Post:
As I said - I just scanned thread titles - win some, loose some.
I did have a look in a couple of the other threads and someone a few months back said something about this project not having done a good job with the actual application development. I think your comments about not check-pointing correctly is a symptom of such :-(

I can't help thinking that the issues you are seeing with the excessive delivery of tasks may be related to having tried to do "something clever" with the server side of BOINC and haven't got everything right. I do know that other projects are no exhibiting the same over-supply issue when using the max-concurrent tag, but seeing the exact messages around a work-call and work-not-call would certainly help Richard understand what is going on and thus either report a bug correctly or point you in the direction of a solution.
32) Message boards : Questions and problems : Problem with "max concurrent" in app config. (Message 103444)
Posted 7 Mar 2021 by robsmith
Post:
Sorry, I forgot to say - this one looks to be a similar problem to yours (from the title)
https://www.kryptosathome.com/forum_thread.php?id=18
33) Message boards : Questions and problems : Problem with "max concurrent" in app config. (Message 103434)
Posted 6 Mar 2021 by robsmith
Post:
You can get newspapers on t'internet nowadays lad!

There are some things one might find rather uncomfortable or unpleasant to do with an i-pad or the like......Wrapping up one's fish and chips being but one of them ;-)
34) Message boards : Questions and problems : Problem with "max concurrent" in app config. (Message 103429)
Posted 6 Mar 2021 by robsmith
Post:
Rather than trying to describe what is going wrong post your logs - Richard may be along soon to ask you to set some of the log debug flags so we can see what is being asked for.
One thing (or is it two things?), how long does a kryptos task take to run (really run) and what is the initial estimate of run time for tasks? This may help people understand where and what is going wrong. (Registration for new users is currently down, so it is hard to get any idea of these things.) In the past (and even today) there are projects for which the runtime guess was a gross underestimate, thus the servers would just keep pushing up excess work based on invalid runtime estimates.
35) Message boards : Questions and problems : Problem with "max concurrent" in app config. (Message 103427)
Posted 6 Mar 2021 by robsmith
Post:
I assume you are saying all other projects are complying with the restrictions you have set, that is x-concurrent tasks and a buffer of no more than 3 hours of work.
That being the case this would appear to be a project that has it's end of the process wrongly configured and is just sending out large amounts of data when only a small amount is requested. A quick look at the project's own forum indicates that there are other people suffering similar (not obviously identical) problems to the one you are seeing, indeed I see you have been quite active in one of the threads, so it may well be better to report it over there.
If this is affecting more projects than just kryptos@home then it could a BOINC problem.
36) Message boards : Questions and problems : Need help putting together a Computer for boinc (Message 103405)
Posted 3 Mar 2021 by robsmith
Post:
After a false start the latest batch of Beta units appear to have gone through OK.

A slight aside - it can get very confusing if one sets a new system straight out into the wilds of Beta testing as one can't be sure any/all of the problems seen are down the application under test or the "nice shiny new" system. So it is better for one's sanity to start off using a "production" project (one with a stable application) fr a few days just to make sure you understand what the new system is doing.
37) Message boards : Questions and problems : Need help putting together a Computer for boinc (Message 103345)
Posted 1 Mar 2021 by robsmith
Post:
This really depends what you mean by "server CPUs" - ranging from the positively ancient four core Intel & AMD offerings up to the current crop of Intel & AMD very high core count offerings. One key thing with almost all server-grade CPUs is that they are very fussy about the type of memory they require (often exasperated by the motherboard you settle on). So when it comes to splashing the cash make sure you budget for not only a lot of RAM but a lot of RAM of the correct type (dare I mention the grief that some of us suffered in years gone by with certain HP & Dell server systems....) Look very carefully at each part of the system and make sure they are "certified*" to work with each other or you could end up with a very expensive doorstop (worst case) or something that has far worse performance than you would expect.


* - Most of the reputable motherboard manufacturers publish lists of memory that should work with a given CPU on their motherboard with particular CPUs.
38) Message boards : The Lounge : Don't know where it should go? Stick it here! (Message 103335)
Posted 1 Mar 2021 by robsmith
Post:
It is a shame that society today is too politically correct, as if it wasn't they would be excellent comedians.


I beg to disagree - real comedians would address them by a more accurate title so as not to besmirch the great and honourable title of "comedian".
(Readers may use their knowledge of the language employed by former great comedians to guess at appropriate titles.....)
39) Message boards : Projects : Asteroids@home: My username unknown, couldn't upload results (Message 103328)
Posted 1 Mar 2021 by robsmith
Post:
They probably do know about this.

Do they care about this?
How far down their list of urgent jobs is it?
Are they in a position to do something about this?

(and a load more questions)
40) Message boards : Projects : bad news everyone, results of the BOINC Collatz project are invalid (Message 103310)
Posted 28 Feb 2021 by robsmith
Post:
Sadly projects that don't do the science properly (within the limits of "current" understanding) bring the whole world of distributed computing into a poor light.
I hope he manages to sort out the errant code quickly and re-run whatever data needs to be re-run. The harder part of the issue to solve is re-establishing public trust and confidence.


Previous 20 · Next 20

Copyright © 2021 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.