Yeah, as
@Rokket said, to be able to stop the render when it's clean enough, you need
progressive refinement checked.
@Faery_Light Your screenshot cut off the right-hand column (bounce numbers); those are important.
Roughly stated, the number of samples determines the relative amount of detail/accuracy of an effect; the number of bounces determines whether the effect is completed or not.
I forgot about bucket size versus render pixel dimensions, as
@quietrob mentioned. For Superfly, the bucket should divide evenly into both the height and the width. So for example, if rendering a 1200x750 frame, you might choose Superfly bucket size as 25, 30, 50, 75, or 150. Notice that 1200/30=40 (no fractions or decimals left over), and likewise 750/30=25.
The reason is that fractional buckets left over at the edges of the frame take as long to render as a full size bucket.
As
@phdubrov noted, the frame size does not need to be the
least common denominator, just a common denominator; likewise, the bucket size does not need to be the
greatest common factor, just a common factor.
For Firefly, try to use integer powers of 2 for the bucket. Anticipating this, I choose Firefly frame size to be a multiple of such a bucket. So, maybe a 1280x768 frame, with Firefly bucket size of 8, 16, 32, 64, or 128.
In my experience, the quickest CPU render times come with a Superfly bucket of 30 or so, and the quickest Firefly with 32.