Posts by William


log in
1) Message boards : Number crunching : Munin setiathome has now also graphs for V8 (Message 1783422)
Posted 5 days ago by Profile WilliamProject donor
That's because of the xml error Andy reported a few days ago.
2) Message boards : Number crunching : Task Preference Not Being Honored (Message 1783418)
Posted 5 days ago by Profile WilliamProject donor
Nonetheless he should be getting v8 if no AP are available with the first setting.
3) Message boards : Number crunching : SETI V8 CPU Wierdness (Message 1783416)
Posted 5 days ago by Profile WilliamProject donor
signal cor caroli i have the image

Might as well try to signal cori celesti... ;)
4) Message boards : Number crunching : Average Credit Decreasing? (Message 1783206)
Posted 5 days ago by Profile WilliamProject donor
In easier words, it is supposed to take the time you took for a task, award you credit according to how efficient you were (compared to all tasks and tasks in your group of tasks) in crunching the task, [I think in theory, you are supposed to get a bonus if you are faster than the average] and then use the time (in relation to how 'big' the task was) to estimate your speed for future tasks (APR).

I'm not sure that was an easier explanation of what it's supposed to do...

In praxi, we have noticed that it falls sadly short of both making a good estimate of your speed (it lacks adaptability) and of awarding credit relative to your efficiency.

In short, the way in which it was implemented (coded) cannot work. It leads to chaotic behaviour.
5) Message boards : Number crunching : SETI/BOINC Milestones [ v2.0 ] - XXIX (Message 1783161)
Posted 6 days ago by Profile WilliamProject donor
My BOINC milestone: 10 years as your BOINC moderator. Go on, say something nice about me. :-)

My signature image links there as well.

wow. congrats. I tried to read the text on your sig earlier ;)
6) Message boards : Number crunching : V8 CUDA for Linux? (Message 1783156)
Posted 6 days ago by Profile WilliamProject donor
Greetings All

Is user Ralph Hyre (beta) Workunit ID# http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=23347475
using a special app, as he is running a version of Linux and is getting what looks to be like OpenCL workunits.

I am a bit confused, or is it because he is a beta tester??????

Regards

SETI@home v8 v8.07 (opencl_nvidia_SoG) x86_64-pc-linux-gnu

whatever he is running meets the specs for that stock app. Or met them in march, he doesn't seem to be active any more.
7) Message boards : Number crunching : Help! No GPU work for Days (Message 1783141)
Posted 6 days ago by Profile WilliamProject donor
also, once you are empty and have repeated 'no task' events, boinc will go into increased backoffs (up to 24h). [mea culpa. it's meant to stop boinc asking for tasks too often]
under normal conditions it can take a few attempts to top up - if you are on a 24h backoff...

each tie a task is reported, those backoffs are cleared, so it doesn't happen if you have tasks left. 'priming the pump' when you are empty can be a bit difficult. I suggest you periodically hit the update button until you get a few.

And yes, if there are few tasks to be had for NV because of lots VLAR you are competing for a very limited resource and must get lucky on your request.
8) Message boards : Number crunching : Panic Mode On (102) Server Problems? (Message 1783139)
Posted 6 days ago by Profile WilliamProject donor
yes what happened is suddenly earlyer the whole project reset with out of pointer errors and asked me to attach a project it killed everything and that was on lunatics then i added seti again and it cleaned out the the project folder completely so i had to reinstall lunatics

sounds to me like you got yourself a new datadir. that would explain some of the stuff.

BOINC stores the whereabouts of its program and data dirs in a registry entry.
If you change the data dir away from the default, but for some reason lose the registry entry, reinstalling boinc will (unless you point it to the previously used dir [which incidentally is how you move data dirs across computers]) go back to the default. the default then of course is completely empty - no projects no lunatics no nothing.
you reattach to the project - you get stock. boinc will also realise that the call comes from a fresh install, it will look up your computers, find the old tasks, find you don't have them on board (cause they are in a different dir) and mark them as abandoned. it will then proceed to give you stock on the original host id wth the original APRs.
when you then reinstall lunatics, the registry is checked for boinc and stuff put in the right place, upon which you go back to anonymous, happily crunching whatever tasks you had.

the part of the code supposed to deal with errors and how many tasks you should be getting if you have lots of errors is about as capricious as the code that selects the fastest app.
sometime it works, sometimes it doesn't.

Life goes on. In the big picture it doesn't matter if one dot is the right colour. I forgot which % of dots needs to be worng for you to notice the picture is getting distorted.
9) Message boards : Number crunching : Lunatics Help (Message 1782895)
Posted 6 days ago by Profile WilliamProject donor
Richard is out, so as one of the other persons involved in the installer:

Hi

I just found this useful thread so can someone answer some questions for me?

1) What benefits does this optimised app offer, compared to the standard SETI apps? (I used to use "crunch3r's" optimised app, ages ago, so I'm aware of what benefits that app gave - is this one any better ?)

we wouldn't call it optimised if it wasn't any better, now would we?

The picture isn't quite that simple though, so I'll break it down by device types.
CPU: stock has a 'lowest denominator' app and an AXV app. if your CPU falls in between, we definitely have a better version. I'm not sure about AVX - the optimised app might still be a little faster than stock.

GPU If you have NV then the installer _currently_ has the same app as stock. That's because for several years Jason as an independent volunteer developer has been providing the NV app to the project. Since stock tends to move a little more slowly, Lunatics installer can be ahead of stock for a while.
ATI same picture. Raistmer along with Urs provide the OpenCL app. Again, the installer may have a newer version (but not right now, we just pushed all we had at the v8 transition.)

installer offers the additional advantage to select exactly what apps to run (like AP on the CPU only) and to be independent of BOINC's erm capricious 'fastest app' selection.

2) I set this up last night with the installer (win_32 v0.44) and I know that I have a Fermi type GPU (GTX580)...but the installer "offered" the cuda32 GPU app...whereas recent tasks I've run (before using the optimised app) were running (mostly) cuda50 tasks on the GPU. What's the difference ?


There's guidance in the readme - the cuda32 flavour is preselected as it's the 'will work in any case' choice. For a Fermi type you indeed want cuda50.

The difference is in the cuda runtime libraries used. newer cards are faster with higher cuda versions. older cards are faster with older cuda versions.
Jason could explain in detail why...

So, do I over-ride the installer and select the cuda50 app ?

Thanks in advance :)

Don't need to override - just run it again and change your selection.
10) Message boards : Number crunching : Say goodbye to SETI@home v7. (Message 1781303)
Posted 11 days ago by Profile WilliamProject donor
at that rate, you are going to run out of size and colour before you run out of tasks :D

you check once a day? care to make a graph? I'd like to make a quick extrapolation.
11) Message boards : Number crunching : Average Credit Decreasing? (Message 1781255)
Posted 12 days ago by Profile WilliamProject donor
ok, so what we really need is somebody with a bucketful of cash, who says 'here have that - but only if you make sure credit works' ?
12) Message boards : Number crunching : Average Credit Decreasing? (Message 1781229)
Posted 12 days ago by Profile WilliamProject donor
No, now BOINC has created the credit monster, I think it has a responsibility to calculate it with the same rigour as the projects calculate their science. And we have a responsibility to report the problems as fully and accurately as we can.

No objections, your honour.

But credit should have a sound mathematical basis and a faultless computational algorithm implementation.
And CreditNew hasn't. Not the latter and I'm still not convinced about the former.

Looking at credit in this detail is like looking at a house that is falling down, has gaps all over the planks and a leaking roof, when the architect used a twig for a ruler and the builders used cardboard for wood...
13) Message boards : Number crunching : Average Credit Decreasing? (Message 1781221)
Posted 12 days ago by Profile WilliamProject donor
[Edit:] @Richard: noticed you have a 970 in with a 750ti in two machines ? both those are likely to claim on the high side for 750ti tasks... (peak_flops_from_wrong_device X elapsed)

I did declare the 970s in my original statement of evidence, m'lud...

But I hadn't picked up from the previous discussion of code that mis-matched GPUs would have that effect (perhaps because I never ran mis-matched GPUs until January). If that's the case, there's no way of applying rigorous mathematics to credit until the server has proper, individual, records of each separate GPU.

On another tack, I'me seeing a remarkably low proportion of shorties in the current Arecibo mix - that's a big plus for my 750s.

please don't mention maths and CreditNew in the same sentence...
Next time I need a RNG I'm just going to use credit.
14) Message boards : Number crunching : Lunatics Help (Message 1780652)
Posted 14 days ago by Profile WilliamProject donor

that looks like you found a place that prints it out. where's that?
much easier than staring at client_state.xml :D

Yep, it's in host properties web page.
Example:
http://setiathome.berkeley.edu/show_host_detail.php?hostid=4517643

indeed. but only for your own hosts. thanks a lot!
15) Message boards : Number crunching : Average Credit Decreasing? (Message 1780648)
Posted 14 days ago by Profile WilliamProject donor
Has this been run up the flag pole to others ????

has what exactly been run up the flag pole? (to whom in particular?)
16) Message boards : Number crunching : Lunatics Help (Message 1780647)
Posted 14 days ago by Profile WilliamProject donor

sure. but boinc has mechnisms for that. it's does keep track of uptime and of active time. and that in turn is used to calculated remaining cache.
it _should_ also be taken in account when fetching work - it certainly is when the work arrives.

if not carrying a large cache but processing it at snail's pace could certinly lead to grabbing large amounts of work that don't get done in time.


Like
Fraction of time BOINC is running 76.80%
While BOINC is running, fraction of time computer has an Internet connection 99.08%
While BOINC is running, fraction of time computing is allowed 99.70%
While is BOINC running, fraction of time GPU computing is allowed 99.65%

that looks like you found a place that prints it out. where's that?
much easier than staring at client_state.xml :D
17) Message boards : Number crunching : Lunatics Help (Message 1780627)
Posted 14 days ago by Profile WilliamProject donor
As far as I'm aware BOINC stops workfetch when suspended.

I can think of a scenario where that might not apply - though feel free to expose the the flaw in this argument (I can think of one of those too, but I leave it as an exercise for the reader).

Modern computer equipment is supplied with energy-saving options active (sleep when inactive, that sort of thing). BOINC also comes with defaults like "only run GPU tasks after computer has been idle for 3 minutes". Couple those two together, and you could - conceivably - come up with a powerful computer, perhaps a gaming spec, which is allowed to download tasks, but only runs them for a few minutes a day.

sure. but boinc has mechnisms for that. it's does keep track of uptime and of active time. and that in turn is used to calculated remaining cache.
it _should_ also be taken in account when fetching work - it certainly is when the work arrives.

if not carrying a large cache but processing it at snail's pace could certinly lead to grabbing large amounts of work that don't get done in time.
18) Message boards : Number crunching : Panic Mode On (102) Server Problems? (Message 1780600)
Posted 14 days ago by Profile WilliamProject donor
I haven't received any GPU tasks at all today since the outage. Nothing but GBT vlars being downloaded. Setting the log options for scheduling shows an acknowledgement of GPU deficit but BOINC refuses to download any GPU work. Something has changed in the scheduler I think. Maybe Eric put something in place that changes the rules for Nvidia. These entries in the log are suspicious and something I've never seen before.

Keith-Windows7

36177 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] reserving 0.330000 of coproc NVIDIA
36178 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] add to run list: 13au10aa.23534.4598.16.43.43_0 (NVIDIA GPU, FIFO) (prio -0.983826)
36179 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] reserving 0.330000 of coproc NVIDIA
36180 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] add to run list: 13au10aa.23534.4598.16.43.95_0 (NVIDIA GPU, FIFO) (prio -0.992389)
36181 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] reserving 0.330000 of coproc NVIDIA
36182 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] add to run list: 14se10ad.23501.4975.12.39.107_1 (NVIDIA GPU, FIFO) (prio -1.000953)
36183 Milkyway@Home 4/19/2016 11:04:24 PM [cpu_sched_debug] reserving 0.500000 of coproc NVIDIA
36184 Milkyway@Home 4/19/2016 11:04:24 PM [cpu_sched_debug] add to run list: de_modfit_fast_15_2s_136_ModfitConstraints1_2_1453826702_38380416_0 (NVIDIA GPU, FIFO) (prio -1.007310)
36185 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] reserving 0.330000 of coproc NVIDIA
36186 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] add to run list: 13au10aa.23534.4598.16.43.167_1 (NVIDIA GPU, FIFO) (prio -1.009516)
36187 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.21706.6234.15.42.25_1
36188 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.21706.6234.15.42.77_1
36189 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.23534.4598.16.43.97_0
36190 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.21706.6234.15.42.27_1
36191 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.23534.4598.16.43.41_1
36192 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 14se10ad.23501.4975.12.39.95_0
36193 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.23534.4598.16.43.115_1
36194 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.23534.4598.16.43.169_1
36195 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.23534.4598.16.43.113_1
36196 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.21706.6234.15.42.95_0
36197 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 14se10ad.23501.8247.12.39.88_0
36198 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.21706.11142.15.42.10_0
36199 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.21706.11142.15.42.163_1
36200 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.21706.11142.15.42.7_1
36201 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 13au10aa.21706.15641.15.42.175_0
36202 SETI@home 4/19/2016 11:04:24 PM [cpu_sched_debug] insufficient NVIDIA for 14se10ad.23501.15609.12.39.174_1


I'm sitting at about 100 GPU tasks on each machine and I should be at 200 tasks per machine since they both have two GTX970's. I'm fully loaded at 100 CPU tasks per machine. I don't think that the MB splitters are only pushing out VLAR GPU tasks right now which is the only other reason that Nvidia cards aren't getting GPU work. Anybody else confirm the scheduler requests?

[Edit] So maybe the spigot has re-opened. I'm getting GPU work again on Pipsqueek, up to about 170 right now. Hope I see the same event happen on the main cruncher. But also seeing the 'insufficient Nvidia' on Pipsqueek also. Very weird recovery from the project outage today. Still think something's changed in the scheduler.


I think boinc is just telling you that it cannot run more tasks on the GPUs you have with the 0.33 and 0.5 setting you made - basically it ran out of GPUs to run more tasks but fore some reason still checked a dozen more tasks as to whether it can make them fit in.
19) Message boards : Number crunching : Panic Mode On (102) Server Problems? (Message 1780598)
Posted 14 days ago by Profile WilliamProject donor
and according to this post from Eric at beta he is well aware of the problem and will be testing how the current NV app fares with guppis.

do people ever look at their acronyms? I keep thinking of them as
20) Message boards : Number crunching : Panic Mode On (102) Server Problems? (Message 1780595)
Posted 14 days ago by Profile WilliamProject donor
Hi,

My GPU WU queue is empty, I'm running MB v8 NV CUDA.

There are 500000+ work units ready to send. The CPU app downloads those guppi vlars just fine.

Do the ATI/AMD OpenCL platforms get guppi VLARS for processing?

If yes then: What shoud I set to plan_class to get GPU work? (To fake I'm running AMD opencl)

In the absence of non vlar work I could do vlars albeit slowly. They take about 14 minutes one at a time.

Petri

EDIT: I just received 20 tasks for my GPU. They are not guppi.
My plan_class is <plan_class>opencl_nvidia_sah</plan_class>


it's not only the plan_class but also the device type (intel amd NV) that boinc determines and passes on. and the vlar filter hinges on the device type.


Next 20

Copyright © 2016 University of California