UVEditor adds a bunch of mesh objects, materials and texture mappings into the document and those take some memory. Also after closing UVEditor those things are still there, not sure if Undo would otherwise work.
However undoing and redoing UVEditor repeatedly seems to increase memory usage so there might be a leak as well.
I would say so far the web broswer is using much more RAM than Rhino I wouldn’t talk about Rhino. 
Close Google Chrome and try again. An available RAM of 16 GB is quite limited - best don’t waste RAM by background tasks.
Hi Micha, how many RAM would you recommand if 16GB is limited for rendering ?
Hi,
As I have limited memory, in these cases I open my ladtop manufacturer software (ASUS in my case) and I free regularly Memory when I see it increase over 85%, it worked, but means that I have to help the machine and survey it… Not really convenient when the rendering lasts more than 15 minutes.
It depends on the complexity of our scenes. My system is running between 20…30GB before I start a rendering. My PC has 64GB and I never got a problem, but I’m using GPU rendering. I think 64 GB is fine and 128GB is best for complex scenes and CPU rendering.
I doubt you need 128GB of RAM for CPU rendering, like I rendered 500 million polygons (with a lot of help from instancing)on an 11GB GPU and CPU rendering isn’t going to be more demanding…and if you try to render something that big on CPU it’s gonna take weeks lol. I once ran into memory trouble with GPU rendering with iray because you need enough virtual memory to be able to swap out(or to be able to address it since you couldn’t access VRAM directly? I dunno) all the 44GB VRAM I had at one time.
16 is too little these days because it’s been an unremarkable amount of RAM for over 10 years now, our phones have that these days, it’s like why not have 64 so you can have 50 Chrome tabs open while working?
The more RAM you have the less you have to swap out. Swapping out to virtual memory (aka page file or swap file) is very slow. I have 128GB RAM for the CPU (and 48GB RAM on each of my GPUs) precisely to get as little swapping as possible.
Yes I know what RAM is for. This was a situation where whether it was a Windows or Iray quirk but with 4 1080ti’s it was failing to render due to not having at least as much virtual memory repeat VIRTUAL MEMORY as VRAM, regardless of actual scene size or actual RAM usage.
Right, you’re talking about RAM on the GPU, which is also what I meant.
Either way, lots of both types of RAM is great to ensure as little paging as possible (or having GPU kernel access host/CPU RAM, which is also slow).
One thing to do is to get rid of most of the utterly useless software.
You mentioned that you have “laptop manufacturer software”, this is essentially bloatware that will eat well into your resources.
This will vary of course, but you should survey the software that is wasting a lot of resource just sitting in the background. I can guarantee that whatever the “laptop manufacturer software” is, is a total waste of system resource and space. You can achieve the same with something like HWinfo. Prebuilt desktops and laptops from major OEMs are massive culprits of installing bloatware.
If you are not in the position to purchase a laptop with 32 GB of memory or more (understandable, mobile price/performance is often absurd), then start with the bloatware.
thanks ! just cleaned a little bit my pc from bloatwares 
I also saved my file in a compact format, from 1BG it turned to 480Mo… BUT I just notice that it is hell when I open this file, Rhino is creation the mesh and my ladtop just turns off even the second time…
I wonder, isn’t it possible to buy an external graphic card to increas
I also noticed that calculating with OPTIX from Navidia card is faster than CUDA
OptiX is using the raytracing acceleration (RT) cores that are part of your GPU die. The CUDA cores are more generalised. In general, it is almost always faster to utilise OptiX with your GPU in rendering. I think(?) that Cycles is highly optimised around its GPU implementation.
Depending on your model, check that you don’t have custom meshes everywhere as well. They are useful for rendering quality, but they may be causing you problems if you have forgotten or made surfaces.
I am curious, given your specialty is Jewellery, if this is normal for such industry in terms of file size. This seems quite large.
If your laptop just turns off you might be running in overheating issue. Make sure you clean out all ducts and openings with compressed air. Maybe even see if you can get all the fan blades cleaned.
In addition to this, and I am not advocating that you do this, but especially with laptops, it can be a good idea every couple or few years to repaste the CPU and GPU, as the paste dries out or leeches.
you mean leaks?
Anyway, repasting is something you probably should let a professional do (and if you are uncomfortable doing the cleaning why not let a pro do that too).
Probably. There’s another word I cannot recall that is probably better. But I am not a linguist.
I will open a new topic to talk about that, indeed, I am starting with Rhino and will get my professionnal training soon, but I start myself ^^
Lots of chains in this model, made of 6086 small polysurfaces links lol, I think that is the core of my problem, not fare to make a machine work hard
That would possibly be 6085 small polysurfaces more then what you need 
if they are all the same why not use one and make block instances from it, you will save a lot of resources .
David it really depends what one is working on. For the computer it makes no difference the world size of the model. For example: I work on one [small] ring right now and it’s nearly 37mil poly… [about 13+GB RAM ]
Yes depends on, and I discovered things today to avoid computer crash and it seems that :
- to accelerate calculating, we need to reduce the number of polysurfaces in order to reduce the number of mesh to upload during rending process
- to avoid computer crash such as GPU is out of memory, we shall keep wirre or shaded view in the active window for the render and in addition, do not show the render window in the render window.
- finally, find the correct picture size that can bare our computer…
talked too fast, out of memory was here ! 
Save small is only good for keeping space on the hard disk. It doesn’t help to keep the usage of RAM or GPU low. It cost time to recalculate it if you open the Rhino file. I don’t use save small.
1 Like