Forums Technical Discussion HQeue Madness

HQeue Madness

   1858   4   1
User Avatar
OneBigTree
Member
378 posts
Joined: Nov. 2010
Offline
 
I had HQueue set up and running for H17. I had the clients running by running the bat file. So far so good.

With H17.5 I decided to set it up again running the services properly. I had all my client checked in and my share set up, all clients logged on with my local user (admin) account.

Today I submitted my first test job. It took 15 min just so submit (A sphere, a grid and a light)! The submission succeeded but none of my client can find the project file.
I checked every thing, now my clients start to disappear from the client list on the server. They go offline but the HQServer still checks them in when I remove them, but flags them as not responding.


The time I have used already trying to get that bloody HQ working is worth more than I make with Houdini alltogether.

I have a project to render and this stupid overcomplicated network rendering is putting it all at risk!

Why can't we not have a simple commandline that fires up Houdini and render a given ROP so we can use it with the render managers we all have running already? Why would I do any job in H if I can not be sure I can render it?

Please SideFX, stop this madness.
Edited by OneBigTree - Aug. 22, 2019 19:22:32
 Report
User Avatar
A-OC
Member
253 posts
Joined: July 2006
Offline
 
We recently tried to setup HQ too. Long story short, we had to hire a network specialist.
 Report
User Avatar
OneBigTree
Member
378 posts
Joined: Nov. 2010
Offline
 
A-OC
We recently tried to setup HQ too. Long story short, we had to hire a network specialist.

I'm so glad you wrote this - it means I'm not crazy
 Report
User Avatar
mrCatfish
Member
731 posts
Joined: Dec. 2006
Offline
 
There is a simple command line renderer that fires up Houdini and renders a given ROP: hrender

Usage:

Single frame:   hrender    [options] driver|cop file.hip [imagefile]
Frame range:    hrender -e [options] driver|cop file.hip

driver|cop:     -c /img/imgnet
                -c /img/imgnet/cop_name
                -d output_driver

options:        -w pixels       Output width
                -h pixels       Output height
                -F frame        Single frame
                -b fraction     Image processing fraction (0.01 to 1.0)
                -t take         Render a specified take
                -o output       Output name specification
                -v              Run in verbose mode
                -I              Interleaved, hscript render -I

with "-e":      -f start end    Frame range start and end
                -i increment    Frame increment

Notes:  1)  For output name use $F to specify frame number (e.g. -o $F.pic).
        2)  If only one of width (-w) or height (-h) is specified, aspect ratio
            will be maintained based upon aspect ratio of output driver.
Sean Lewkiw
CG Supervisor
Machine FX - Cinesite MTL
 Report
User Avatar
OneBigTree
Member
378 posts
Joined: Nov. 2010
Offline
 
Thanks mrCatfish. This works only from within Houdini, no? How would I integrate this into renderpal?

Anyway I got one client back up and running using the .bat file.
It turns out HQueue is extremely slow at processing everything. Not only does the submission take ages, the local client needs about half an hour to create 50% of the actual render jobs. The testscene sequence would have rendered 5 times in that time. Server and client run on the same machine in this case for testing but the job submission was already slow as hell no matter where I installed the server.
Edited by OneBigTree - Aug. 23, 2019 10:47:58

Attachments:
task_slow.JPG (11.9 KB)

 Report
  • Quick Links