Windows 7 vs Windows 10?
rodriguez1222_bda0b64bf2
Posts: 52
So my current PC was running windows 7, and I did some tests prior to installing Windows 10. This is on the same scene, same figures, textures, etc.
Windows 7: Daz Studio opens in around 45 seconds. The scene loads in about 70 seconds. Render time is about 30 minutes for Iray to reach 1500 samples and stop
Windows 10: Daz Studio opens in about 180 seconds. Scene loads in 8 minutes. Render timer is 6 hours for Iray to reach 500 samples... I fell asleep waiting, and when I woke it was only at 500 samples and still going so I stopped the process.
Both were rendering in GPU but with windows 7 the fan on my card was booking it. When the render started I could HEAR the fan kick on. Windows 10, it picked up a little but not really much.
I did update the drivers for 10 direct from the Nvidia site.
Any advice would be appreciated. Thanks
Any thoughts on what I can do to speed up 10? or at least Daz working with 10? I know my hardware could use an upgrade, but a few days ago with 7 I was happy with the way everything was working with Studio. Now it's slow as hell and forget about using the auxilliary window with Iray on, it straight doesn't do anything at all.
Could it have anything to do with DirectX 12? I mean, I doubt it, but I'm spitballing here... Maybe a registry issue, or I dunno...
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Something I just noticed...
So in 7 when I hit render, my computer was more or less unsable as every resource seemed to be going to the render. With 10, it's almost like nothing is happening. The test renders I did I left the computer alone, but now Im trying a new scene and it's chugging along rendering, but I'm able to surf, use photoshop, and I'm not noticing anythying slowing down.
Is there a way to force 10 to allocate more resources to D|S? Maybe that would speed the render?
Without the system specs there is not much anyone can do.
? check the Virtual Memory?
Increasing Virtual Memory in Windows 10
Sorry about that. I meant to put it, but considering it worked a few days ago flawlessly with 7, I didn't consider it could be a hardware problem.
AMD FX 8150 8 core processor 3.6g
32gb Ram
Geforce GTX 970 4gb
Thanks Catherine. I did the VM tweak already. Pretty much goes as a first step when doing a fresh install of windows. Much appreciated.
Just noticed 10 is only utilizing 4 cores. Going to do the tweak to force it to use all 8... see what happens from there.
Even as bad as Bulldozer was I doubt that's the issue. Opening an application is essentially single core.
It is possible that some other system component is having an issue with Win10. I'd check the motherboard vendors site for any updated drivers and if you know how update the BIOS as well.
If none of that helps you could try a reinstall of DS.
The rendering seems an awful lot like it dropped to CPU so I'd also run a very basic render, a single primitive with a texture and make sure thecard is being used by DS.
I did the tweak. TM is showing 8 core usage now. Everything is opening faster, so that at least helped. Like you said Kenshaw, I don't get why that would have done any good... but it did.
BIOS! yeah I'll try to flash that. That's the one thing I didn't do since installing 10, and there is a BIOS update. Thanks for reminding me.
Render-wise... D|S is showing full GPU usage. The TM is showing between 80% and 100% GPU usage, when it hits 100% the CPU usage goes up. So there are little spikes in CPU usage when the GPU maxes out.
Thank you so much for your help. Going to update the BIOS, see what happens.
No go. I did the flash but it was the same BIOS version I had.
What else can I try?
a reinstall of DS and a clean install of the GPU driver are the next things I'd try.
Also post a log from the start of a really slow render.
OMG what a stupid windows feature... 3 hours into a render and the computer just restarts... No warning, no pop-up, just update and restart without informing me. Just like Defender quarantining files without a warning... Defender was the first thing I nuked lol. Now I have Update and auto restart disabled. Who in Microsoft Land thought thought this was a good idea?
2020-06-10 06:23:36.702 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 995 textures, 70 lambdas (23 unique)
2020-06-10 06:23:36.768 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (39 light sources with 16904 triangles, 1 instance) took 0.001s
2020-06-10 06:23:36.768 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2020-06-10 06:23:36.801 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2020-06-10 06:23:36.801 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2020-06-10 06:23:36.801 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2020-06-10 06:23:36.801 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2020-06-10 06:23:36.802 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2020-06-10 06:23:36.802 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2020-06-10 06:23:36.821 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2020-06-10 06:23:36.830 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2020-06-10 06:23:36.830 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2020-06-10 06:23:37.128 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2020-06-10 06:23:37.128 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce GTX 970)
2020-06-10 06:23:37.136 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-06-10 06:23:37.136 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend progr: CUDA device 0 (GeForce GTX 970): Processing scene...
2020-06-10 06:23:37.218 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Geometry memory consumption: 164.835 MiB (device 0), 0.000 B (host)
2020-06-10 06:23:37.218 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Using OptiX Prime version 5.0.1
2020-06-10 06:23:37.218 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing OptiX Prime for CUDA device 0
2020-06-10 06:24:01.337 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Texture memory consumption: 1.039 GiB for 197 bitmaps (device 0)
2020-06-10 06:24:01.337 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Importing lights for motion time 0
2020-06-10 06:24:01.338 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing light hierarchy.
2020-06-10 06:24:01.735 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Light hierarchy initialization took 0.397s
2020-06-10 06:24:01.738 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Lights memory consumption: 2.855 MiB (device 0)
2020-06-10 06:24:01.758 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2020-06-10 06:24:02.084 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : PTX code (157.553 KiB) for SM 5.2 generated in 0.325s
2020-06-10 06:24:02.084 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Materials memory consumption: 844.379 KiB (GPU)
2020-06-10 06:24:02.429 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : JIT-linking wavefront kernel in 0.093s
2020-06-10 06:24:02.491 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : JIT-linking mega kernel in 0.054s
2020-06-10 06:24:02.492 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce GTX 970): Scene processed in 25.355s
2020-06-10 06:24:02.497 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce GTX 970): Allocated 27.001 MiB for frame buffer
2020-06-10 06:24:02.560 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce GTX 970): Allocated 864.000 MiB of work space (1024k active samples in 0.063s)
2020-06-10 06:24:02.568 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce GTX 970): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-06-10 06:24:04.014 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : Allocating 1-layer frame buffer
2020-06-10 06:24:04.664 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00001 iterations after 27.528s.
2020-06-10 06:24:05.640 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00002 iterations after 28.503s.
2020-06-10 06:24:07.205 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00003 iterations after 30.068s.
2020-06-10 06:24:08.769 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00004 iterations after 31.633s.
2020-06-10 06:24:10.640 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00005 iterations after 33.504s.
2020-06-10 06:24:11.926 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00006 iterations after 34.790s.
2020-06-10 06:24:13.491 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00007 iterations after 36.355s.
2020-06-10 06:24:15.065 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00008 iterations after 37.929s.
2020-06-10 06:24:17.218 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00009 iterations after 40.082s.
2020-06-10 06:24:18.221 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00010 iterations after 41.085s.
2020-06-10 06:24:19.786 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00011 iterations after 42.650s.
2020-06-10 06:24:21.354 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00012 iterations after 44.218s.
2020-06-10 06:24:24.502 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00014 iterations after 47.366s.
2020-06-10 06:24:27.626 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00016 iterations after 50.490s.
That log is fine and the initial render rate is way faster than you said (roughly 1000 iterations per hour)
yeah that render ended up being quicker. Thankfully it looks like it's in good shape again.
This is awesome.
THANK YOU!!
So to recap, just in case anyone else has this issue
I Adjusted the Virtual Memory
Flashed the BIOS
Updated the Graphics Driver
Installed the Nvidia CUDA package
Did the Windows 10 Tweak to force it to read all 8 CPU cores
Disabled Auto Restart
And within D|S I changed the Iray render settings to Max Samples: 15000, Max Time: 0, Render Quality Enable: Off
Hope that helps the next person.
Thank you for your help. I really appreciate it!
? Nvidia CUDA package ? Is that this = CUDA 11
Do we just install it or do we do something with it once it is installed?
How do you force W10 to read all 8 6 CPU cores?
To force the CPU read
Thats the one I installed was CUDA 11. I have no idea if that helped or if it was a technical placebo but it did make my card actually sound like it was working when I hit render.
Also, the CUDA 11 package, it shows up in my Nvidia Control Panel now. I don't think it was there before.
Okay, thank you. I've downloaded that huge package [2.5GB], will install it and hope my computer doesn't blow up [jk].
Wow, it gave me an option up to 12 processors?? Was only sitting on 1, so I upped it to 4. Obviously I'm learning this one as I go along today.
sockets 1
cores 6
logical processors 12
So which is the best choice me to put there, 4, 6 or go for all 12? or ?
Your guess is as good as mine :) I'm new to tweaking W10. I would google your Mobo and see what it can handle.
Right, thank you :-)
Anytime!
MTFBWY
I cancelled the installation of CUDA 11 - didn't look like something I should be needing and it was going to mess with the video card drivers. I work with the theory if it ain't broke, don't fix it.
However to get the computer [laptop] to use more of the cores it has sounds like a good thing. I tend to think that whatever is there, should be in use anyhow. Why it defaults to such a low value I don't know. I did read a serious warning though which I will repeat here for the curious, do NOT mess with the memory. [the one that shows up on that same popup] Somebody was giving out bad advice to up it to full and that's very bad. It doesn't mean what people think it does, and if it's put to full, it will use all the memory to full before overwriting stuff and that ends up with a frozen computer of course because it won't have anything left to write with.
STOP!
Do not muck about with things you don't understand if you're not having problems, EVER!
The CUDA dev toolkit is absolutely not required for users. It is, as it specifically says, the toolkit for developers.
You should never, ever, under any circumstances mess with the boot options in msconfig unless you know exactly and precisely what you are doing and why. You NEVER need to reduce the number of cores available to Windows, except for testing or if a specific program will not even load and tech support for that product directs you to do so.
Specifically @Catherine3678ab your system is reporting 1 cpu with 6 cores and 12 threads. If that is what is actually installed then DO NOT CHANGE IT! If you did change it change it back immediately.
Sorry... yes. I took it for granted that ppl are intelligent and wouldn't mess with too much if they arent comfortable with it. Having built dozens of computers from the ground up, tweaked them and debugged them for decades now, I am very comfortable that I won't fry anything. If I do break something I'm confident there isn't anything I can't fix.
That being said I'm not naive enough to think I know everything, just that I'm sure I can push limits that I don't undersatand and fix it if I break it. For me, the Cuda Dev kit gave me some options I didn't have which, now that I am messing with it, is letting me create pathways to D|S that I didn't have before. Is it useful? Sure. Is it easy? Not even a little if you don't know what you're doing and you aren't comfortable with messing with CMD prompt and/or VS.
Okay, thank you very much for the alert. Hope it's okay to wait for a massive copying of backup files to complete first.
@ kenshaw011267 For what it's worth I had looked at some other places about this number of cores being used, so it's good to know not to mess with them contrary to their advice.
These are 2 pics from my computer, would seem that while I thought I had changed the 1 to a 4, and rebooted the computer. Now it popped up showing still at 1. So I left it at one and now it's saying to reboot the computer? It started at 1. Is that where it should be then?
The drop down goes from 1 to 12.
Yo!!! Now it is only saying "1" ... what did I do and how do I get that 12 back? tia
Got 'em back. Found a nice page over at Microsoft. Apparently nothing should be ticked in that little box and also to be careful 'cause that first general thing before Boot options has a nasty habit of first appearing with the option to start in some very unhelpful right now set up. Almost 'safe mode' but not quite, geez. Anyhow, nothing is broke and nothing blew up :-)
I'm pretty good at tinkering and figuring out some things, but I think I shall leave this matter alone for now.
Catherine,
Glad you got it worked out. That screen shows you have 1 socket but 6 cores. I have 8 cores, but initially that screen showed 2 cores, 4 logical cores. I changed it to 8 cores as it should be. I know I have an 8 core CPU, my BIOS shows an 8 core CPU, Windows System Manager shows an 8 core CPU... but the Task Manager was only showing my computer utilizing 2 of my 8 cores. Initially I thought maybe when it maxes out to 100% it'll show 2 more cores or something as maybe an energy saver or something... However, when gaming, rendering, using Photoshop, Blender, Unity, etc I was finding it would max out, everything would basically freeze....
I'm talking right clicking on my desktop would take about a minute for the display menu to come up... After coming from 7 where everything was as fast as thought to not being able to play Java games on Win10, there was absolutely a problem.
Changed it to 8 cores , now it's displaying 8 cores and the speed is back to what it was before I 'upgraded' to 10.
For me, even with 7, the Aux Viewport with Iray would take forever. With the CUDA package and a few system processes written in VS I can actually get real time out of my Aux Viewport. It's not as fast as I've seen some people have, but it's better than not being able to use it at all.
At least it'll do for now until I get a better video card.
Glad you have your computer working better for you too :-)
I don't use the Aux Viewport very often but for some tasks, like making shaders, it is invaluable.
Likely the system detected that there was only one socket and wouldn't take your changed setting but this could have forced you to reinstall Windows.