Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

kgoossens

Performance boost idea's

Hi I'm looking for Idea's on how to increase modeling performance for my courses I teach.

There are many things that come to mind.

-Using wrangle nodes.

-Building custom versions of some existing nodes with limited functionality such as a vop's ray node.

-Using attribute transfer instead of ray sop

-Using point clouds.

-Avoiding foreach nodes.

-creating a minimalistic representation of the final result for fast turnaround times.

-unloading of nodes

Any other things, techniques for a specific solution, like the "Group in Mesh" on Orbolt from Sergei Bolisov. would be very welcome to hear about.

Cheers,

Kim

1 person likes this

Share this post


Link to post
Share on other sites

Recently I found foreach with variatioin attribute usually make it way faster (so, make it possible to use ;)) than just iterating all prims/points. It doesn't always work. But if you know when you can use it, it can be really powerful.

Example file and otl attatched.

foreach_with_vari_attrib.hipnc

yb_curve_tools.otl

yb_timeshift_pp.otl

Share this post


Link to post
Share on other sites

Hi, kgoossens. thank you for many tips. :)

I am especially curious of your last suggestion. How can I unload a node? What does it mean?

Share this post


Link to post
Share on other sites

You have to right click a node and click Unload. A different flag is shown on the node.

1 person likes this

Share this post


Link to post
Share on other sites

Hi magneto, I tested it, and it works! Thank you. But still didn't get what it actually mean.

So.. give me more hint, please? :)

Share this post


Link to post
Share on other sites

So when you unload it, the memory of the node will not be cached AFAIK. Imagine a very expensive operation that stores copies of the meshes to calculate a final result. You don't necessarily want to keep them in memory after it's done cooking.

Share this post


Link to post
Share on other sites

To my knowledge unloading is only really effective if you are not doing a recursive or manual operation on or from an unloaded node.

Otherwise it will have to recook the node constantly and with recursive nodes it can increase cooking time significantly.

Starting from Houdini 13 you'll be able to create polygonal geometry using Wrange nodes.

Things like making curve connections between points based on distance is really neat, and it can be made 100x faster & memory efficient with a wrangle node then doing it with a for-each node.

Share this post


Link to post
Share on other sites

Starting from Houdini 13 you'll be able to create polygonal geometry using Wrange nodes.

Things like making curve connections between points based on distance is really neat, and it can be made 100x faster & memory efficient with a wrangle node then doing it with a for-each node.

That's great! Thank you for letting me know!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now