A question about --- CPU code generated.

Right now I am running an overclocked I9 9900K at 4.7 and working with a 360mm AIO cooler. So far I haven't broken past 71C even at 100% usage. I am sort of seeing how much I can get out of this since I've just upgraded my cooling as of today.

My question is this - When I see "CPU CODE GENERATED 0.052s", sometimes that image renders directly after that, other times it just slams to a halt. I don't mean the program crashes, simply that the clock keeps ticking. Is this an indicator that the image is not going to render?

 

Other times (Smaller projects with scene optimizer) it will work just fine. My CPU and GPU function perfectly, I am just wondering if I demanded too large a render - does this mean it won't work?

Comments

  • When CPU code is generated it means the render will use the CPU, either because you've selected that (bad idea generally) or the scene is too big for your GPU's VRAM.

  • mclaughmclaugh Posts: 221

    When CPU code is generated it means the render will use the CPU, either because you've selected that (bad idea generally) 

    Unless I'm misunderstanding you … not necessarily.

    CPU-only, I concur, but at least for me, "CPU code generated" shows up as the second item in the pre-render processing when both CPU and GPU are checked in the Render > Advanced tab, followed by 3-4 lines ending with (GPU). Once the render start, GPU-Z shows the GPU running at 95-100% and Task Manager shows the CPU load in the 15-20% range, which I presume means that the bulk of the render is being done by the GPU.

    Haven't timed GPU and GPU+CPU renders of the same scene to see how +CPU affects performance, but my impression is that GPU+CPU finish faster. (Guess I know what I'll be doing this afternoon.)

  • I have no idea about your setup but I've run several tests and GPU+CPU was always slower than GPU only.

Sign In or Register to comment.