I've been testing out EC2 cloud rendering (or trying to) with Houdini 13, and all my test jobs come up “failed” with the error:

/bin/sh: line 0: cd: /opt/hfs13.0: No such file or directory

And sure enough, when I log in to the EC2 instance, there's no installation for Houdini 13, just various flavors of 11 & 12.

Any thoughts on this? Is the queue logic on my end somehow not initializing the EC2 instances correctly - or is EC2 not set up for H13 yet?

I've seen it there, two weeks ago H13 was on cloud.

I just gave it a quick try and I can see H13.0 on the cloud.

What region are you submitting jobs to?

What OS are you running on?

Cheers,
Rob

I discovered that the 32-bit image sesi has on EC2 doesn't seem to include H13. (Or didn't at the time I checked.) Forcing the instance to the 64-bit image worked. Amazon's had 64-bit small/micro machines for over a year now, iirc - so there's really no reason to have a 32-bit image at all.

Also discovered that EC2 rendering is crazy slow. I was getting 15min+ times for frames that were taking 3-4min on my local workstation. Even with a large instance. And that's not counting the spin-up time & the time to upload the files.

Ah yes. We dropped support for the 32-bit image. It should not be possible to start a 32-bit cloud instance from the latest Houdini 12.5 or 13.0 since we removed it from the Machine Type drop-down menu.

Cheers,
Rob

I checked H13.0.237, and in python2.7libs/cloudsubmit.py I see the line:

processor_type = (“i386” if instance_type in (“m1.small”, “c1.medium”)
else “x86_64”)

I'm not sure how the menu items map to instances - presumably “1 EC2 unit” is small, and “5 EC2 units” is medium?

Shoot. That's a bug alright. It is fixed in tomorrow's build (13.0.255).

Thanks meeotch!

Cheers,
Rob

Anyone use the cloud to sim 32 GB or 64 GB sims?