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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Yeah. I think you can combine them as long as they're the same type from the same manufacturer, but it can be hard to find compatible sticks if you wait more than a year or so. I'm pretty sure I ended up just replacing my old ones entirely.
And that's a good argument for getting more now, really. If it turns out the minimum requirements aren't enough, you might end up spending more in the long run than just buying it up front.
I don't know how much slots exist. Those are pre built, hot selling, generic and good for email sending, receiving, branded PC for general purposes with 4gb and few are 8gb ram. Last update is PC shop will call when available after few days.
Trouble with page files generally comes from two things:
1. Too little RAM in the system (which means Windows is going to need to access the page file a lot more)
2. Not enough space on the harddisk, or not enough space allocated to the page file.
Windows will always try to assign some harddisk space for pagefile usage. Given a large enough harddisk, that shouldn't be a problem. Given enough RAM, Windows may reserve space for a pagefile, but won't actually use it. Page files are the sole reason why I once started frankensteining my old hard-disks to new computers. The additional space to store other data was a bonus, but simply having a seperate harddisk for the page file which wouldn't interfere with other read/write made things run a lot smoother.
A lot of pre-build and branded computers instead make a partition on the regular drive for this purpose. And while that improves the speed of page-file usage somewhat, it can't hold a candle to having a seperate dedicated physical drive (HDD or SSD) for that purpose, especially when that page file is used a lot due to being low on RAM. Oh, and make sure it's an internal drive that you assign for your page file, not an external one, as external drives go into a sleep mode when they're not accessed, and require as much as ten seconds to spin up again, which is very noticable if your computer runs out of RAM and suddenly needs to start writing to it.
Check your memory usage while you are rendering one of your "normal" scenes. I'm running 24GB on an i7 windows 10 laptop. I can usually get away with comicbook style renders having 12-16 characters in an environment with everything running 1024x1024 max maps 3delight, diffuse and specular maps only. I use Daz default shaders on anything not using transparency, ubersurface for transparent/illuminated surfaces. Rendering usually eats up 90-100% of available memory. If I'm running any other program while rendering runs there's a good chance of Daz crashing. Going over 20 characters usually means converting them to props. Going that route I've rendered the same type scene with around 40 characters with the same texture map set up.
More memory is never overkill. If it's available, you'll wind up using it. My next box sill probably start at 64GB.
No. You can add any sticks to any other. You may not get the full rated speed of the RAM but they will work. But since most people have no idea how to set XMP profiles, and most pre builts don't have XMP profiles set, RAM speeds are just advertising numbers in most cases.
Those days are really really over. Windows wants the pagefile on the boot drive. The best solution is to leave around 100Gb free on the boot drive, at least 50gb, and set the pagefile to be system managed.
You still can move it: https://winaero.com/how-to-move-page-file-in-windows-10-to-another-disk/. Best solution is still to have enough RAM, so Windows won't really need it though.
My own opinion is that reccommended should be at least 10GB. Minimum should be 6 - and specifically emphasised that 6 is a long way from ideal. If things continue as they have done the last year say, then it isn't going to be that long before the mimimum will be 10GB.
Windows will use a pagefile no matter how much RAM you have. You can verify this yoruself. Open performance monitor and graph the pagefile.
I am not going to experiment it but curious if I install 2GB RAM and set page file size 128GB will I get the benefit of 130GB RAM? Or machine will hang frequently? I am currently considering 64 GB physical RAM after learning from Microsoft
....When large physical memory is installed, a page file might not be required to support the system commit charge during peak usage. For example, 64-bit versions of Windows and Windows Server support more physical memory (RAM) than 32-bit versions support. The available physical memory alone might be large enough...... The available physical memory alone might be large enough to do this.
https://docs.microsoft.com/en-us/windows/client-management/introduction-page-file
I've seen Windows VM's with 512Gb of RAM and nothing at all running but background tasks still hitting the pagefile. I have literally no idea what that article is talking about. Anyone can test this out for themselves. Stuff is getting shuffled into and out of virtual memory all the time.
I suspect the activity is Windows doing auto defragging but don't know for sure. I have always set page file to let Windows manage the size as it needs.
Microsoft is not the ONE to turn to when challenging the boundaries of the computer. Often you spend a lot of time getting the system to follow the rules YOU need it to follow instead of how MS thinks it should operate. Starting with W98 and W2K Microsoft has taken the operating systems and how they work further and further away from the needs of someone testing the boundaries.
There is no harm in having a pagefile, you just get enough RAM that it is not needed in such a way that you would notice it being used.
If you are concerned about the number of read/write operations in SSD, there are much more "dangerous" features in Windows, at least if you follow Microsoft in how the system should be set up and operate.
In simple terms, the greatest computer performance will be with a sufficient amount of physical memory. How much is sufficient depends on what the user is doing. If the physical memory isn't large enough then Windows will use the page file. Worth mentioning is that the page file will be slower than physical memory, even with an SSD. If you go to the Task Manager in Windows you can look at the performance tab and get an idea of how much physical memory and page file is being used. In simple terms, the more that the operating system has to shuffle things off to disk (page file), the slower the computer will seem to run. This latency will be less with an SSD due to the faster data transfer but it will still be slower.
If you are rendering in iRay and using the GPU for the render then the physical memory requirement is lower because the GPU uses memory on the graphics card. If the iRay render (or 3Delight render) is using the CPU for the render then the amount of physical memory is a concern because the textures and other data is residing in physical memory and not in the graphics card memory.
There is an argument (or belief) that Windows will find a way to use the page file no matter how much physical memory you have. The key is to have enough physical memory for the operations that you are doing. I have always maintained that memory upgrades are the cheapest bang for the buck in terms of performance, followed by an SSD.
Yeah... Windows is happily playing with itself unless you force it to behave, indexing is also one of it's favorite games.
"GPU for the render then the physical memory requirement is lower because the GPU"
Though my suspect physical memory requirement will be much more than GPU memory because, physical memory will require to transter those data to GPU memory. Otherwise a huge page file will generate temporarily everytime when a render going to start.
Not a problem unless you have more VRAM than RAM and you are rendering huge scenes, and there is really no point in having that little RAM
I can't speak to that in depth as I don't have an iRay supported GPU. My renders are all CPU based. That said, I would like to see some hard data (such as a graph over time of physical, page file and GPU memory usage). You make an interesting point.
I think the bar is set way tooo low in the requirements for the software. I would appreciate recommendations that were a bit more honest about gpu.
You can say that again... 1-2GB RAM, 128-512MB VRAM and 1GB harddrive space were maybe adequate some 10 years ago, today it may be enough for installing and opening the application, but that's about it...
That will not work. The page file is not the same as ram memory. It's too slow.
Realistically no Windows 10 machine meant for more than browsing email and watching youtube should be lower spec than this:
4c/4t (some recent generation)
8 Gb RAM
512Gb persistent storage
Adding Daz Studio and iRay on top of that would bump that up a lot:
16 Gb of RAM (minimum if you have the cash go for more but you can get by with 16, I do. I have a lot more on my work machine and I do not notice any difference when I build scenes at work vs. home).
1 Tb of persistent storage (no idea what DS really takes up on its own but 3D assets take up a lot and most people get a lot of them and there are a lot of free ones out there so even starters can blow through a lot of storage)
Minimum, IMO, 6 Gb VRAM Nvidia GPU. I know people have 4Gb, and smaller GPU's, but that way lies heartache and pain for newbies buying new assets.