Goodbye for good


Advanced search

Message boards : Number crunching : Goodbye for good

Author Message
keputnam
Send message
Joined: 31 Mar 05
Posts: 15
Credit: 109,233
RAC: 130
Message 13812 - Posted: 9 May 2015, 10:01:10 UTC

Hoping against hope that you had finally gotten blender to play nice in a multi-project environment, I accepted new work

Bad choice

I've got an app_config.xml file that limits BURP to four of my twelve "CPUs" (hyper threaded hex-core)

The one WU I got, while saying it was using 4 CPUs, was actually using eight!. I say this because BOINC manager showed only four other single threaded WUs active while blender was running. On top of that, it was using 7.5GB of RAM. Really??

Additionally, after 15 hours, BOINC manager showed an estimated 240 hours remaining (after an initial estimate of 54 minutes) with a three day deadline !

I know that you won't "kill kittens" if we miss a deadline, but the BOINC scheduler doesn't, and will put your WUs in panic mode, thus completely hosing the scheduling of other projects that DO play nice


Sorry. but I probably WONT be back


As an aside, I might point out that with my measly 60K credits, I rank at the 95th percentile of all crunchers on this project.


Seems like a whole lot of folks just gave up on you without bothering to leave a post here


____________

Profile DoctorNow
Project donor
Avatar
Send message
Joined: 11 Apr 05
Posts: 392
Credit: 2,168,338
RAC: 25
Message 13816 - Posted: 9 May 2015, 14:03:16 UTC - in response to Message 13812.
Last modified: 9 May 2015, 14:22:30 UTC

I dare to write an answer to that, even that I'm sure you won't like it (and maybe not reading it at all since you're already gone). ;-)

Hoping against hope that you had finally gotten blender to play nice in a multi-project environment, I accepted new work
...
snip

Well, if someone wants to crunch seriously here he has to give up a little from the other projects, that's a given.
Sessions do get different deadlines because of different hardware requirements, and it's a part of the project "philosophy" to have results back as fast as possible. If you can't accept that, you're wrong here.
Furthermore, BURP is not an easy project from the beginning and not every user can get along with it. If you whine about every single thing that's not playing nicely with your own plan then you're wrong here also, because this isn't a project in production mode where you can just hop and go from time to time, there can be always surprises here. It needs a bit of experience and you're not getting it like that.


I've got an app_config.xml file that limits BURP to four of my twelve "CPUs" (hyper threaded hex-core)

The one WU I got, while saying it was using 4 CPUs, was actually using eight!.

Well, app_config.xmls are no guarantee that it always works. Have you checked that the config is still correct? There was an application update early in the year, maybe that's the main problem.

On top of that, it was using 7.5GB of RAM. Really??

Additionally, after 15 hours, BOINC manager showed an estimated 240 hours remaining (after an initial estimate of 54 minutes) with a three day deadline !

I guess you had a WU from session 2647. This is a memory and computive intensive session and also - have a look here - there is a problem with time estimation from Cycles etc. Nothing really to worry about because the tasks are not really need to take as long as the estimation says.
Be sure to check requirements for sessions before you crunch them. If you don't like it - cancel it.

but the BOINC scheduler doesn't, and will put your WUs in panic mode, thus completely hosing the scheduling of other projects that DO play nice

I notice you seem to give a lot for the scheduler. The whole thing is completely crap anyway, I wonder that you didn't notice that in all the years you are crunching, and it seems it's almost as long as I do when I look at your projects.

As an aside, I might point out that with my measly 60K credits, I rank at the 95th percentile of all crunchers on this project.

Seems like a whole lot of folks just gave up on you without bothering to leave a post here

Well, that doesn't say anything. It's just that the majority of crunchers are probably not used and in to rendering and animations.
____________
Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

M0CZY
Avatar
Send message
Joined: 31 Jul 09
Posts: 24
Credit: 279,094
RAC: 0
Message 13821 - Posted: 10 May 2015, 7:42:27 UTC
Last modified: 10 May 2015, 8:03:58 UTC

What upsets me is that out of my last 18 work units, 14 were marked as invalid.
http://burp.renderfarming.net/results.php?userid=9917

I'm not leaving though, as some of my work units were valid, so I must be doing something right.
____________
The biggest threat to public safety and security is not terrorism, it is Government abuse of authority.

Bitcoin Donations: 1Le52kWoLz42fjfappoBmyg73oyvejKBR3

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4483
Credit: 2,094,806
RAC: 0
Message 13823 - Posted: 10 May 2015, 9:10:09 UTC - in response to Message 13812.
Last modified: 10 May 2015, 9:15:45 UTC

while saying it was using 4 CPUs, was actually using eight!. I say this because BOINC manager showed only four other single threaded WUs active

Did you verify this using the process manager? Or did something happen that made BOINC simply not schedule enough WUs to fill the CPUs at that point? Did it say "4 CPU" or "8 CPU" in the client?

On top of that, it was using 7.5GB of RAM. Really??

You can configure this in the computing preferences either directly on the host or on the website. It is a "Memory: Use at most X%"-setting.

panic mode

I remember when this feature was in development - it was called panic mode not because there was a reason to panic (never panic as long as you have a towel!) but because the scheduler had detected a situation where it had to re-order the downloaded workunits on the client in order to fulfill the timing requirements of lower latency projects like BURP.
There's a lengthy technical discussion on the terms "long term" and "short term" project debt where lower latency projects mostly play into the long term debt, but in essence it boils down to this: Yes, as soon as you download a BURP workunit the client will focus on delivering the results as fast as possible or the WU will be rescheduled if it hasn't started working on it by the deadline (that's kinda what the deadlines mean here, btw - starting deadlines). You decide how often work is downloaded using the "Resource share" project preferences.
The name stuck, and now it is called "panic mode" in the UI as well.

Goodbye for good

Thanks for playing along for 10 years - I wish you all the best

Profile DoctorNow
Project donor
Avatar
Send message
Joined: 11 Apr 05
Posts: 392
Credit: 2,168,338
RAC: 25
Message 13824 - Posted: 10 May 2015, 9:14:01 UTC - in response to Message 13821.

What upsets me is that out of my last 18 work units, 14 were marked as invalid.
http://burp.renderfarming.net/results.php?userid=9917.

That link isn't working for us, but judging from your statement and looking into your comps I can deduce that you mean your Linux machine.
Typical problem that on all these invalids you crunched against two Windows machines, which (by default) doesn't work.
Something similar was asked before, and Janus just wrote this statement some minutes ago.
____________
Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

M0CZY
Avatar
Send message
Joined: 31 Jul 09
Posts: 24
Credit: 279,094
RAC: 0
Message 13828 - Posted: 10 May 2015, 10:36:51 UTC

Having read the post you mentioned, I'm happy to continue even though my work is mostly invalid, because it is helping to develop the new, improved Cycles validator.
____________
The biggest threat to public safety and security is not terrorism, it is Government abuse of authority.

Bitcoin Donations: 1Le52kWoLz42fjfappoBmyg73oyvejKBR3


Post to thread

Message boards : Number crunching : Goodbye for good