Jump to content

Search the Community

Showing results for tags 'performance'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Lounge/General chat
    • Education
    • Jobs
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering
    • Compositing
    • Games
  • Coders Corner
    • HDK : Houdini Development Kit
    • Scripting
    • Shaders
  • Art and Challenges
    • Finished Work
    • Work in Progress
    • VFX Challenge
    • Effects Challenge Archive
  • Systems and Other Applications
    • Other 3d Packages
    • Operating Systems
    • Hardware
    • Pipeline
  • od|force
    • Feedback, Suggestions, Bugs

Found 12 results


    Creating a node takes ages. What could be the problem that is making it so slow? It did this after the latest update (updated 15.5.632 to 15.5.674) Please note that we already tried to install versions as far back as 15.0 and until the latest version of 15.5. The problem keeps occurring even without virus scanners and windows defender being turned off. It also doesn't matter if it is installed on a SDD or on a HDD and all the drivers are up to date. Even if all the preferences have been deleted (in the documents directory) it stays the same and it also doesn't matter on which Houdini License server it's running: in Standalone mode or not. I'm running out of ideas to what the problem could be. If you know the solution or have an idea what it could be, let me know! Please ignore the audio in the example video below, it is in a noisy classroom with students discussing different nodes (not related to what you see, you can watch without audio)
  2. This operator allows you to run an OpenCL kernel as part of your SOP network. Depending on the GPU, some operators can be orders of magnitude faster than even VEX. In this case the OpenCL code is 144 times faster than VEX on GTX 970.
  3. Volume convolution on the GPU using OpenCL. For 27M voxels using 100 iterations, OpenCL is 650 times faster than C++ and 12525 times faster than VEX.
  4. Laptop Quadro or GTX, pros & cons

    Hello people! I am buying a laptop workstation to use while traveling for a few months later this year and I don't know if I should buy a laptop with a Quadro or a GTX card in it. What are the pros & cons? (price excluded) Does Houdini run better in general on Quadro cards? Also, feel free to drop some laptop recommendations if you have any! I've got my eyes on a Dell Precision 7710. Best regards, //Simon
  5. viewport slow; pc build check

    Hi all, Completely new to Houdini and this forum! I am Cinema4D-er learning Houdini on a brand spanking new PC. It's also my first build so not-so-bright choices may have been made... It seems my viewport/perspective view is taking up so much time (Red-zone on the Performance Monitor). Figured I'd start by checking my hardware, so please judge my build for anything that is off... (Don't judge me ) Thanks for your help i7-7700K Asus Prime Z270-A Corsaie LPX DDR4-2133 MSI GeForce GTX 1060
  6. First things first: – This is not a “why Mantra is so slow” topic. In fact, Mantra is my first renderer, so until now, for what I read, it seems pretty fast and good. – I came from a digital product design background and I’m really new to 3d and Houdini. – I’m using a MacBook Pro for learning which I know its definitely not the best machine to work with 3d stuffs. (Specs: Mid 2012, 2.3Ghz i7, 8GB RAM, GeForce GT 650M 1GB) So after this (not so happy) presentation, lets talk about my problem: I was doing a tutorial from Niels Prayer about how to make a geometry react from an audio file and after that I've tried to render a sequence of 860x540 images. I waited 14 long hours for about 12 secs of video. Is this normal for my computer specs? I forgot to cache the geo, but I don’t know if this could be a great factor to get a faster render, could be? I've read some topics about Mantra settings from Odforce and SideFX forum and found some interesting tips about how to get better and faster rendering trying to get down the pixel sample values, increase the max ray samples and tweak the noise level to an acceptable value. So I’ve attached a hip file with my Mantra settings, and my machine can render this frame in about 3:13 min. This is current the best I can do in terms of speed and quality. Do you guys can check it out my file and see what I can do to get a faster render? Please feel free to hit me with tips on how to get the best of Mantra and Houdini in general. Thanks a lot. Cheers, render-test.zip _render_test_1.exr
  7. Liquid sim performance

    Hi, with several scenes I have alwas the same problem. I start simulation of a volume or flip sim what works fine for the first few frames. Then the cpu usage drops down and only one core is used most of the time. For every frame, the cpu usage goes up for a few seconds only, then it drops again. So I suppose it has to do something with my general setup. My current simulation is a breaking bottle with liquid what looks like in the attached image. I'd really appreciate if anyone could have a look at the scene and give me a hint what I'm doing wrong. The file is a bit larger (23 mb) so I placed it here: bottle archive Thanks for any ideas.
  8. Hello, I was recently testing a flip simulation on a workstation with dual xeon 2630 v4 processors 10 cores each clocked at 2.2 GHZ, to my astonishment my laptops quadcore 4770HQ @2.2GHZ delivered ,not the same, but better FLIP simulation times. Can anyone explain to me why this is. I heard someone tell me something about threading. Can someone give me some insight on which nodes are multithreaded. with the smoke solver its stranger when my division size is higher like 0.2 the quadcore processor absolutely destroys the dual xeon, flying past the simulation. but when I start reducing that division size the xeon processors start to catch up and eventually when I am at a final render division size the xeons are ahead of the quadcore. Also when I cache out a simulation and check task manager when the cache is somewhere in the middle of the simulation(presumably where the flip simulation has the most particles to solve), task manager shows the cpu hovering around 2-3 %.
  9. OpenCL Smooth SOP

    Smoothing geometry on the GPU using OpenCL. In VEX it has to be done in 2 steps where the same thing can be achieved in OpenCL in one step using barriers [khronos.org]. For a 822K polygon model, it's over 500 times faster than VEX on GTX 970 for 1000 iterations, and over 600 times faster for 10K iterations. Timings are recorded separately as there seems to be some overhead when running them one after another. Special thanks to SESI.
  10. The most powerful wrangle operator due to the sheer fire power of the HDK. Performance increase can vary from a few times to thousands of times depending on the scenario.
  11. Hi there! I have a rapid question... there is some particular setting/option or check in Houdini (15) for improve the peformance with hadware? Actually I have: AMD FX 8350 @ 4GHz 32 GB of Ram ddr3 GTX 970 4GB (especially on this section) ssd pro evo OS: win 7 I see some time the "auto-update" of viewport is a few slow.... in alternative is change more the performance from 970 to 980TI or change more if I pass to Linux (fedora/ubunto or centOS) ? Thank you for now Matteo
  12. Remote desktop

    Hi ! I got an office space where i have the machines /server /fast interneto..when working past dinner time or at unreasonable hours (often) I do it from home, by using RDC (remote desktop connection) on win7, it works well with most apps, but Houdini wont run trough it. It runs using TeamViewer,,,but is sloooooooooooow. I have a gaming video card at home and nothing too fancy at the office, which works fine, i don't know if this is a driver issue (got latest nvidia drivers) or some configuration i can change in houdini? thanks O/.