Recent Posts

Pages: 1 ... 3 4 [5] 6 7 ... 10
41
Rendering in the Cloud / 5 Steps to Move to the Google Cloud
« Last post by Render Guru on June 06, 2016, 04:41:07 PM »
Moving to the cloud can be daunting; often organizations struggle understanding where to begin and the steps required to realize a migration. In this one hour webinar, Google's migration architect, Peter-Mark Verwoerd will walk through a framework on how to assess cloud migration. Though the course of this presentation, you will also become familiarized with the services offered by Google Cloud Platform.

https://www.brighttalk.com/webcast/10619/205217
42
Developer Customization / Re: Hostorder by custom CPU-ranking
« Last post by Alexander on June 02, 2016, 08:09:32 AM »
This is an excellent tip.

For what it's worth, there also exists +host.processor_speed and +host.processors.avail.  You can combine them in a host_order like so:

+host.processors.avail,+host.processor_speed

... which would mean, "Choose the machines with the fastest processors AND the most number of currently available processors (e.g. those processors not reserved by other jobs)".

Having said that, Alexander's suggestion is also perfectly valid and some may prefer it, as it is somewhat more concrete than the multi-key host order I've suggested, which is a bit too "black-box" for some.

Thanks for the tip, Alexander!

Thank you for the kind words!

Question about "+host.processors.avail", if the user has designer-license, will that one work or will it just think that the worker has 1 cpu?
43
Developer Customization / Re: Hostorder by custom CPU-ranking
« Last post by BrianK on June 01, 2016, 09:30:05 PM »
This is an excellent tip.

For what it's worth, there also exists +host.processor_speed and +host.processors.avail.  You can combine them in a host_order like so:

+host.processors.avail,+host.processor_speed

... which would mean, "Choose the machines with the fastest processors AND the most number of currently available processors (e.g. those processors not reserved by other jobs)".

Having said that, Alexander's suggestion is also perfectly valid and some may prefer it, as it is somewhat more concrete than the multi-key host order I've suggested, which is a bit too "black-box" for some.

Thanks for the tip, Alexander!

44
Developer Customization / Hostorder by custom CPU-ranking
« Last post by Alexander on May 29, 2016, 04:27:40 PM »
Maybe this can help someone.
Scenario: You want to have the hostorder based on cpu. Ex Arnold-render etc

The job properties
Host Order: +host.comprank

qbwrk.conf on supe:
add this to each worker
worker_properties = "host.comprank=<INSERT NUMBER HERE>"

To find the comprank number I made a little python script. Not the prettiest code... :-)
Code: [Select]
import multiprocessing, cpuinfo, decimal, socket
host = socket.gethostname()
info = cpuinfo.get_cpu_info()

speed = info['hz_actual']
speed = speed[:-4]
speed = float(speed)

amount = multiprocessing.cpu_count()
rank = amount * speed
rank = decimal.Decimal(str(rank))
rank = int(round(rank,0))
line = host + ' ' + str(rank)

f = open('\\\\SERVER\\\\qube\\ranking\\ranking.log','a')
f.write(line + '\n')
f.close()

edit \\\\SERVER\\\\qube\\ranking\\ranking.log to where you want it saved.

module cpuinfo can be found here:  https://pypi.python.org/pypi/py-cpuinfo

Run that script on each machine, one at the time.

This script could probably be done so that it writes direct to the qbwrk.conf. ;-)

Enjoy
45
Announcements / Qube! 6.8-3 released
« Last post by jburk on May 25, 2016, 04:06:21 AM »
This is a maintenance release of the Qube! Core/Supervisor/Worker/ArtistView/WranglerView products.

This is a recommended release for all customers running Qube v6.8.

Please see http://docs.pipelinefx.com/display/RELNOTES/PipelineFX+Release+Notes for complete release notes.
46
Check out the latest work from Moonbot Studios for Samsung
47
Video of GCP event in London May 6, 2016

https://vimeo.com/165583576
48
Jobtypes and Applications / Re: Nuke(cmdline) job runs fine but Nuke(loadOnce) fails
« Last post by BrianK on April 11, 2016, 05:07:08 PM »
You see the nuke license being returned so quickly simply because Nuke has closed.  Running Nuke in "load one" mode should not change the license used by Nuke while being run by Qube.

We would need to see job logs to see what's causing the failure.  This case would best be handled by regular support (by emailing support@pipelinefx.com).

In lieu of regular support, take a look at the job logs (visible through either GUI), and look for any error messages.  Feel free to copy/paste any error messages here.

-Brian
49
Announcements / Qube! 6.8-2 released
« Last post by jburk on April 07, 2016, 01:03:28 AM »
This is a maintenance release of the Qube! Core/Supervisor/Worker/ArtistView/WranglerView products.

This is a recommended release for all customers running Qube v6.8.

Please see http://docs.pipelinefx.com/display/RELNOTES/PipelineFX+Release+Notes for complete release notes.
50
What the title says. I've attempted to render the same job both ways and the cmdline version finishes while the loadOnce seems to fail as soon as Nuke launches without any hint in the logs as to why. Do the two jobtypes use different types of Nuke licenses? The cmdline option opens Nuke with the -x flag and thus only uses a nuke_r (render-only) license. When I try a loadOnce job I see in my license server logs that the node checks out a nuke_r license as well, but then instantly returns it and the job fails. Is it looking for an additional interactive license, like nuke_i? I'd love to not have to re-load the Nuke scene every single frame like the cmdline jobtype does, but I only have nuke_r licenses for my farmers. Is this why loadOnce jobs are crashing?
Pages: 1 ... 3 4 [5] 6 7 ... 10