MegasXLR Render

MegasXLR Render

Description

Megas Shows off it's Chest Weapon
A short animation of a complex build of a model (Megas) moving and transforming to reveal a huge weapon enclosed in it chest cavity.

Message boards : Comments and discussion : 1950

Author Message
Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4483
Credit: 2,094,806
RAC: 0
Message 15253 - Posted: 24 Sep 2017, 13:24:03 UTC

This session got stuck in an unfortunate bug in the upload handler and was recently recovered.

It is now re-purposed as a client-test of the new 5.12 client (Blender version 2.79) for Linux.
Also, it has a very long scene preparation phase and a very short render phase.

mmonnin
Send message
Joined: 21 Mar 17
Posts: 3
Credit: 71,288
RAC: 27
Message 15255 - Posted: 24 Sep 2017, 21:08:09 UTC - in response to Message 15253.

Quite a few invalids. Not sure if its the new app version or the render. This task has 7 invalids:
https://burp.renderfarming.net/workunit.php?wuid=3233455

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4483
Credit: 2,094,806
RAC: 0
Message 15256 - Posted: 25 Sep 2017, 6:04:40 UTC

Or some performance changes made to the validator yesterday - definitely taking a closer look at this when it is done. It looks like all the differences are confined to one channel in the output and almost always the last one.

But yeah, it could also be just the render that is noisy in some way.

mmonnin
Send message
Joined: 21 Mar 17
Posts: 3
Credit: 71,288
RAC: 27
Message 15257 - Posted: 25 Sep 2017, 10:04:21 UTC - in response to Message 15256.

At around 70% completion for 1950 there were several changes to the tasks. They no longer used more than 1 thread but grabbed all available threads from Boinc Manager. On my 2p The CPU time (which adds up all cores) never went above elapsed time. Single thread the whole time. They were also much longer due to this.

Before 70% completion the tasks took about 2.5min before using more than one CPU thread with very little on the progress bar. Memory usage climbed. After 2.5min the progress bar went up quickly.

Some different observations I saw with 5.12.


Post to thread

Message boards : Comments and discussion : 1950