Since blender is supplied the same for render farms, powerful machines & low end machines, the burden of proper usage falls onto the user.
If there's a specific file, use case that you can share about And optimize the operation of nodes!, it'd be better.

What? Optimize blender! It shouldn't crash system! Stop excuses!

@CHET (cheteron), could you provide a simple file showing the problem?

Also keep in mind that this bug tracker is only for bugs and errors.
While we do continue to work on improving performance in general, potential performance improvements are not handled as bug reports.

To improve performance, consider using less complex geometry, simpler shaders and smaller textures.

I wrote above. Render settings:
Resolution 5000*5000 or more. In compositing add denoise node. When blender try denoise, the whole system stops responding.
Need manual limits for memory and cpu

The issue you're experiencing is most like memory related, not CPU related. If it was CPU related, then the entire system should freeze if you used the denoise node on any scene at any resolution. If you would like to test what happens if you limit CPU resources, you can do that by opening Blender and your scene, then open the task manager (Press Ctrl+Alt+Delete and select "Task Manger"), select the "More details" drop down, Select the tab at the top labeled "Details", find Blender, right click it and select "Select affinity" and untick a few (not all) of the boxes and confirm the change. Then render your scene. Now Blender will only run on a percentage of your CPU cores. Re-opening Blender will reset the affinity so don't worry about setting it back to normal.

As for putting a limit in place for RAM, it could be done, but I don't believe it will be on by default. And when enabled, I believe compositing would just fail rather than continue compositing.

Are you able to run some tests for me.

1. Run the test with limited CPU access (described above). Does it still freeze?
2. If your computer still freezes, what happens if you leave your computer for a while? (E.G. 10 minutes) Does it finish the compositing/denoising?

Also, in your original report you state that the issue occurs in Blender 2.90. Did you test with Blender 2.83 or 2.82a? And did they produce the same results?

No crash here, just 2:57 staring at a progress bar at 0% before it was done.

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 376.51

Blender Version
version: 2.90 (sub 2), branch: master, commit date: 2020-05-15 19:12, hash: rBeaf7d36d66e5

In T76790#932691, @Alaska (Alaska) wrote:

Also, in your original report you state that the issue occurs in Blender 2.90. Did you test with Blender 2.83 or 2.82a? And did they produce the same results?

2.83, 2.0 - same results.

PC freeze, and i waiting 10-20 minutes, then restart system, and render without denoise

@CHET (cheteron) with you being able to reproduce the issue with in 2.90, 2.83 and I presume 2.82a, and nobody else being able to reproduce the issue, then we must assume the issue is caused by your computer not Blender.

Yes, the Blender developers can put limits in for how much RAM and how many CPU cores the Intel denoiser can use. But if these were to be implemented, then you wouldn't be able to use the compositor on these high resolution scenes or you would be able to use it, but it'll be extraordinarily slow. That may seem like a better option than your computer freezing and you having to turn the computer off and on again to fix it. But Windows has systems in place to stop these kinds of things from happening. They just don't seem to be working in your situation. But once again, that's not a Blender issue, it's a Windows issue.

It's also possible that you're experiencing a hardware issue. The only way we could tell was if you ran tests on other operating systems (E.G. Linux) or a fresh install of Windows. But once again, that's not a issue with Blender, that's a issue with the hardware in your laptop.

I'm sorry we're unable to help you out with your issue.

Yes, the OIDN denoiser is very memory hungry indeed. However, there's at least 1 thing blender itself can do to potentially mitigate this (if this is truly an out of memory situation): Use the OIDN API setting which limits memory.

OIDN exposes a "maxMemoryMB" setting that blender can set and by default it's set to somewhere around 6GB. Perhaps we need to hook that up and expose a system preference to see if it potentially helps the situation?

https://openimagedenoise.github.io/documentation.html

int |		maxMemoryMB |	6000 |	approximate maximum amount of scratch memory to use in megabytes (actual memory usage may be higher); limiting memory usage may cause slower denoising due to internally splitting the image into overlapping tiles, but cannot cause the denoising to fail |

@Jesse Yurkovich (deadpin) The issue is that Blender shouldn't be causing the entire system to freeze when using the Intel denoiser at any memory usage setting because the page file system exists. This makes me believe the issue is more to do with Windows or the hardware. We also have to consider that once the denoising is complete, there's still a massive multi-gigabyte image file that needs to be stored in RAM. So if 6GB of denoiser is enough to cause issues on the users computer (assuming it is a out of memory issue), then the 5000x5000 resolution image after denoising is also something to consider as the cause for a out of memory issue.

As for implementing an option to control memory usage for the denoiser in the Blender settings, I will leave that up to the Blender developers.

Can u add option limit? Without without third-party resources.
I have seen smart memory limits on other programs, that allow program not to take more than necessary.

In T76790#933016, @CHET (cheteron) wrote:

Can u add option limit? Without without third-party resources.
I have seen smart memory limits on other programs, that allow program not to take more than necessary.

Sadly, I do not know how to add a memory limit as I'm well experienced in programming. This will need to be looked over by the developers. It should be noted that reports made at https://developer.blender.org should be made for bug reports. Feature requests should be made over at https://blender.community/c/rightclickselect/.

Also, Blender is currently setup like "other programs". It's using only what it thinks it needs. Optimizations can and are being made to reduce memory usage in Blender.

@CHET (cheteron) I have added you as a subscriber to a task created to add a memory limit to the Intel denoiser (D7758). Thank you @Jesse Yurkovich (deadpin). You will most likely hear news from the developers on whether or not this should be added to Blender in that task.

Hopefully this patch can help you assuming it gets accepted.

It should be noted that I still believe your issue isn't Blender related, but something to do with Windows or your computer hardware. However, having this option available may give you the option to work around the issue in the meantime.