Second try for a stress test: 5 - 10th of May 2010
We'll try a second pass at rendering the heavy, but extremely nice looking architectural scene. Once we manage to get this render done, we'll be looking to move into supporting the 2.5 render engine and clear up the queue. We'll also be providing new versions of the Renderfarm.fi distribution of Blender simultaneously.
PS. This should mean that we will also have a Mac version of the BURP client running for the first time officially.
- prodigal_son's blog
- Login or register to post comments
Yep, pretty heavy scene here.
My PC occasionally becomes unresponsive and lags a bit, so I decreased the cores and put restrictions on the memory usage. Sometimes single job takes up to 4 hours to complete and on average consumes 1.2+ gigs of ram, which is a personal record for ORE. Anyhow, I am happy that the whole thing is stable and runs well with constant progress. I am very curious to see what the scene looks like when we finish it.
Cheers =)
My comp is on for days, off for nights. So haven't seen any crashes. But I did put out an bug report to boinc section of forum,
It seems the recent stress tests have hit a bug in the server code. The code that normally filters computers based on how much memory they have did not work correctly for sessions with 2GB memory requirements. As a result, workunits were sent to machines that couldn't handle them without becoming unresponsive or laggy. Similarly each machine may have started too many simultaneous rendering threads.
BURP has now been patched and things should be back to normal.
As a little teaser you can use the BURP online "realtime" preview (or CATS for that matter) to see what the session looks like even before it has finished rendering:
http://xmlrpc.renderfarm.fi/img_handler.php?session=195&frame=1000&width=400
There are 2 session running on the server 195(2Gbytes) and 200(32MB)
This client is memory limited to 606MB. it should get session 200. But it doesn't get it.
So this client is idle.
28-5-2010 10:13:22 Open Rendering Environment Message from server: No work sent
28-5-2010 10:13:22 Open Rendering Environment Message from server: Blender needs 2048.00 MB RAM but only 606.37 MB is available for use.
Part 2
When after many retry if finally get session 200 it also get session 195
The server know the client have to small memory.
28-5-2010 9:05:47 Open Rendering Environment Message from server: No work sent
28-5-2010 9:05:47 Open Rendering Environment Message from server: Blender needs 2048.00 MB RAM but only 606.37 MB is available for use.
But it still give project 195 with 2GBytes to the client. The boinc terminate this session.
28-5-2010 9:06:05 Open Rendering Environment Aborting task ses0000000195frm0000001692prt00005_1: exceeded memory limit 651.18MB > 606.37MB
Session 200 run as it should without issue
28-5-2010 9:13:41 Open Rendering Environment Started upload of ses0000000200frm0000000120prt00002_0_0
The session is getting really near to the end now. What can I say: fantastic. Now the funny (tee-hee) part: Jerico is claiming it needs to be rendered again, apparently because there were some little mistakes in the scene. We'll do that later. ;)
Well this scene sure is proving to be one huge stresstest for the clients. I think we're really on the limits of what we can expect from the service in it's current 32bit implementation phase. How are you guys coping out there? I've seen a couple of Blender crashes on one machine here at Laurea UAS.
Julius Tuomisto Project Administrator Laurea SID Networks, Espoo, Finland Tel. +358-50-4135412