Get ready to BURP

[NeoGen]

Mar 23, 2006
Another backup will be done monday the 27th of March together with a very large system software upgrade.
During this upgrade the website may become slow or stop responding. If everything goes well another set of tests will be started Tuesday.
Also welcome to the 275 new users who have joined since the EoPA test started!

Here's another chance for us to see Burp in action!
And don't forget that account creation is still open. You can register either through the boinc wizard or here:
http://burp.boinc.dk/create_account_form.php?teamid=16

[Beerknurd]

ok, I signed up. Right now I am running uFluids and Predictor. I will run Burp once I get established in these 2 projects. Then I will do QMC@Home.

uFluids is taking my Dual Core about 9 hours to run 2 WU's. Which of these projects has the shortest work units??

QMC
uFluids
Burp

It takes me a little over an hour to run 2 WU's in Predictor.

[NeoGen]

Burp is unpredicatable... its workunits can take as little as a few minutes to as much as several hours, all in the same render job.

I thought uFluids would be faster nowadays, but I haven't run it in a while. QMC workunits also take quite a bit I think.
Have you considered Leiden Classical? Or widening a bit more the gap between you and Brucifer in SZTAKI.

[Lagu]

Hi

Beerknurd, watch this link as drezha have found for helping me understand why QMC@Home is so hard to be done:

http://qah.uni-muenster.de/projectinfos2.php

Lagu ;)

[Empty_5oul]

BURP generally depends on what memory you have aswell as the CPU. I found it using up to around 900meg when rendering. (all WU so far have taken my 3200+ about 10/15minutes)

[AMD-USR_JL]

When it used that 900 meg was ur system slow and unresponsive? It always does that on mine, I opened the task manager and no cpu was being used so i just suspended burp, does it take a sec to start crunching? The first time it caused a viscious cycle on my pc. I had my ram optimizer set to free ram if it got below 64mb, it just kept trying to free over and over. Maybe that was the problem, guess i should turn the ram freer off next time.

[Empty_5oul]

my system was actually fine.
Whilst rendering which is exactly what BURP does frame by frame most pressure is on the total RAM to store it all and then process it.

My machine was working as usual for standard operations - just email and browsing.
Just to push my machine and see what would happen i opened a few graphics and applied effects (to 2048x1024px images) and then it was slow. I will proabably just run BURP when i am not at the machine (depending what i am doing).

-- you could always apply the wait 3 minutes of no user input before starting BOINC

[NeoGen]

It was only this last render job that required loads of RAM, all the previous ones I ran didn't have this problem. They must have tried to up the complexity a notch or two and see if the people could cope with it.

And the most amazing is that each workunit is no more than only a part of 1 frame, usually 1/4, or 1/9th of a frame I think. They make something like multi-tile rendering to split each frame in sections and give a piece of frame to each person, because one whole frame at the complexity and resolution level they require would take a day or more in a single computer.

I didn't get to see, but I heard this last test had plenty of semi-transparent (and at the same time) reflective objects, with plenty of light sources to make up for alot of complexity on the scene. This certainly does up the complexity a few notches, because blender is a raytracer renderer, so it has to simulate the precise path of each individual light beam across the whole scene with all the reflexions and refractions and stuff... (and each light source produces probably thousands of individual light beams...)

[AMD-USR_JL]

Alright, i turned off my ram optimizer. I am going to be ready for the next test on Tuesday. We should be able to stomp the other teams, AMD is the best for rendering frames, that's why gamers go AMD. I remember they tested the AMD dual core and Intel dual core on Adobe premiere and the AMD rendered and encoded the same frames 20mins faster.

[NeoGen]

Now that you mention dual cores... I'd be afraid to use Burp on a dual core, unless you got alot of RAM. Imagine a dual core running the last render job, crunching two workunits at once... each taking some 900 megs of RAM :shock: