![houdini software houdini software](https://cdn.conceptartempire.com/images/06/5374/00-featured-houdini-software.jpg)
Total Cache Memory is set to 80% of total RAM to avoid system crashes (25GB).
Houdini software software#
Houdini Software System Requirements, RAM Caching: Comparing 32GB RAM vs. The Grain and Pyro tests do not seem to impact RAM usage at all. The other interesting observation is that the FLIP simulation utilizes 77-90% of the RAM as it simulates and writes to disk.
![houdini software houdini software](http://cdn.techgyd.com/2015/04/Houdini-animation-software.jpg)
This is surprising as I thought reading back from disk would tax the system somewhat but it didn’t. I also tested playback from the disk cache and there doesn’t seem to be any additional performance hits there either.
Houdini software pro#
This corresponds to a peak write rate of approximately 322 MB/s – far below the 2,300 MB/s write capability of the 512GB Samsung 970 Pro, and roughly 65% the write capability of most SATA3 SSDs, though this is an approximately 50% greater data transfer speed than most traditional 7200 RPM Hard Drives are capable of.īefore testing we discussed benchmarking a 2x 970 Pro RAID0 cache disk array for these simulations, but this was unneeded: the amount of time it takes for Houdini to simply calculate the simulation is much longer than the amount of time it takes to write to disk. As each frame written to disk was nearly 1GB, the disk performance spiked to 14% every time the sim frame completed its calculation in Houdini then wrote to disk. The highest utilization occurred with the FLIP simulation. The most interesting observation is that the OS disk was never utilized above 14% for any of the caching tests. Disk caching is written using the File Cache node attached to the DOP I/O or DOP Import nodes and written to bgeo.sc format. These results are for caching to the drive that also contains the OS. Writing to disk (Cache) is being conducted on high resolution simulations to compile the longest data set. This is being done in the DOP Network node’s Cache tab. In the RAM cache tests the cache memory is set to 80% of total RAM to avoid system crashes. Disk caching is written using the File Cache node attached to the DOP I/O node and written to bgeo.sc format. The disk cache tests are being conducted on the Samsung 970 Pro M.2 drive. Hardware acceleration is disabled for these tests thereby focusing the simulation calculations fully on the CPU and caching exclusively on the hard drive or RAM. I’m testing the influence of hard drive speed and RAM capacity on Houdini simulation caches. 512GB Samsung 970 Pro NVMe m.2 SSD (OS Drive).2x NVIDIA Geforce GTX 1080 Ti 11GB GPUs.Houdini Software System Requirements Test Configuration: Special thanks goes to the meticulous Curvin Huber for leading our testing and Houdini benchmarking. Today we present Part II in the series, the role of cache disk and RAM in a Houdini workflow. Last week we shared Part I of III exploring Houdini Software System Requirements, we looked at how different hardware configurations performed rendering Flip, Grains and Pyro scenes with a focus on Houdini’s built-in render engine Mantra.