Announcement

Collapse
No announcement yet.

Progressive sampler low cpu usage

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Progressive sampler low cpu usage

    is it normal that progressive sampler doesn't use 100% cpu power after some passes? ...more or less towards the end of the rendering?
    I'm not very used to progressive sampler as I always used bucket ...that instead stays at 100% all the time
    Alessandro

  • #2
    Yea pretty normal. As far as I remember progressive sampler is meant to get u quick preview not final render quality. The sampler uses less cpu the more of image is finish. It has the same issue with DR too. So use it for preview and Bucket for final. Unless something changed since.
    CGI - Freelancer - Available for work

    www.dariuszmakowski.com - come and look

    Comment


    • #3
      At the end of the render, when there are only a few pixels left, the work can't be distributed efficiently among all CPUs, so some of them will remain idle. Somewhat similar to the "last bucket" effect.

      Best regards,
      Vlado
      I only act like I know everything, Rogers.

      Comment


      • #4
        Thanks, good to know everything is working as expected

        One more question just to understand:
        does every parameteres (min, max and noise) of the progressive sampler work exactly the same way as for bucket? so, except for time, do same values lead to same level of noise?
        Alessandro

        Comment


        • #5
          Originally posted by zeronove View Post
          does every parameteres (min, max and noise) of the progressive sampler work exactly the same way as for bucket? so, except for time, do same values lead to same level of noise?
          Yes, this should be the case.

          Best regards,
          Vlado
          I only act like I know everything, Rogers.

          Comment


          • #6
            I remember being very confused about the fact that if I put in something like 30 max samples (instead of the default 100) the progressive render stopped when ANY one pixel in the scene had reached the 30 and didn't like only stop rendering there and keeps rendering the rest. It was some time ago but do I have some error of memory or thinking here? Nowadays I put it on 1/1000/0.005 just to be safe. The issue is then of course that mostly my scenes wont "finish" rendering but have to be cancelled and manually saved since the 1000 is such an insanely high number that nothing much happens anymore in my scene after a certain amount of samples and there is no point in letting it render any longer.
            Software:
            Windows 7 Ultimate x64 SP1
            3ds Max 2016 SP4
            V-Ray Adv 3.60.04


            Hardware:
            Intel Core i7-4930K @ 3.40 GHz
            NVIDIA GeForce GTX 780 (4096MB RAM)
            64GB RAM


            DxDiag

            Comment


            • #7
              Originally posted by Art48 View Post
              I remember being very confused about the fact that if I put in something like 30 max samples (instead of the default 100) the progressive render stopped when ANY one pixel in the scene had reached the 30 and didn't like only stop rendering there and keeps rendering the rest. It was some time ago but do I have some error of memory or thinking here? Nowadays I put it on 1/1000/0.005 just to be safe. The issue is then of course that mostly my scenes wont "finish" rendering but have to be cancelled and manually saved since the 1000 is such an insanely high number that nothing much happens anymore in my scene after a certain amount of samples and there is no point in letting it render any longer.
              There shouldn't be any need to put 1000 there anymore and you can keep the max subdivs at 30.

              Best regards,
              Vlado
              I only act like I know everything, Rogers.

              Comment

              Working...
              X