Loading...
> >

renders making comp slow to a crawl

UpiriumUpirium Posts: 722
in Technical Help (nuts n bolts)

Last weekend (i think) a power outage destroyed both my D drive and part of my C Drive. The D Drive is where I had all my programs installed but the guy who fixed it told me not to do that becuase it will slow things down. 

Now that I've reinstalled Daz on a new, more space C Drive I'm noticing issues. It isn't really any faster now on the main drive and it lags more with renders. I used to be able to pretty freely move my mouse when in preview render but sometimes I can't. The mouse lags. Last night when I rendered a scene I noticed that I couldn't do much. I was trying to chat on discord and the mouse kept lagging and switching between discord channels was taking forever. 

It's using up 100% cpu and something like 80% memory. I have 32gbs of memory. Nothing has changed in this PC except the hard drive and it's now windows 11 instead of windows 10. All of the other hardware is exactly the same. 

It's been so long since I installed daz on my old hard drive I don't remember if I had some kind of settings changed? I have turned off CPU Fallback because I know that used to lag my PC horribly if it happened to start rendering on the CPU. 

Before I used to be able to run both daz and photoshop at the same time while rendering. Now I can scarcley run discord. 

Comments

  • Richard HaseltineRichard Haseltine Posts: 108,079

    I would say that sounds like a GPU driver issue, except that with GPU fallback off you would get no render at all if the GPU dropped out or couldn't be used.

    Having applications on D: would slow down loading if D: was a mechanical drive and C: an SSD of some kind, but it would usually slow down basic operation. 

    32GB isn't a lot of system memory, it may be that DS or something else is running out of memory and paging to disc (which, even with an SSD, would be slow) or it may be that having apps on C: you now have competition between different things wanting to write to/read from C: that is acting as a bottleneck.

  • UpiriumUpirium Posts: 722

    Richard Haseltine said:

    I would say that sounds like a GPU driver issue, except that with GPU fallback off you would get no render at all if the GPU dropped out or couldn't be used.

    Having applications on D: would slow down loading if D: was a mechanical drive and C: an SSD of some kind, but it would usually slow down basic operation. 

    32GB isn't a lot of system memory, it may be that DS or something else is running out of memory and paging to disc (which, even with an SSD, would be slow) or it may be that having apps on C: you now have competition between different things wanting to write to/read from C: that is acting as a bottleneck.

     

    i have updated my 3060 to the latest studio driver the last I checked, but I don't know if my CPU has current drivers? It's kind of an old CPU. Do you mean the CPU or the GPU drivers? I ask because you mentioned 'gpu' fallback i'm assuming by accident. 

  • felisfelis Posts: 5,771

    It is CPU fallback. Richards fingers has glitched.

    CPU upgrade is less important.

    If you look in the log Help > Troubleshooting > View Log there you can see if you have used CPU or GPU or both, when you have done a render.

  • Richard HaseltineRichard Haseltine Posts: 108,079
    edited August 24

    felis said:

    It is CPU fallback. Richards fingers has glitched.

    Right, sorry.

    CPU upgrade is less important.

    If you look in the log Help > Troubleshooting > View Log there you can see if you have used CPU or GPU or both, when you have done a render.

    Yes, I had meant to say - CPU Fallback is reelvant only if you don't have the CPU selected as a render device.

    Post edited by Richard Haseltine on
Sign In or Register to comment.