How will sending large amounts of information to /dev/null affect the performance of the computer?

Question

linux

I still do not understand the meaning of the "great abyss". When information is sent to null, does it cease to exist? And how does this affect computer performance?
Is it possible to compare the $Recycle.Bin folder on Windows to null on Linux?

Answer 1

Is it possible to compare Masday's recikler folder with null?

I won’t tell you here, I don’t know what kind of folder it is (which is the first one)

I still don't understand the meaning of the great abyss.

Well, for example, you can wrap the stream with ordinary messages (stdout) there, so that only error messages (stderr) would be displayed on the screen. streams still have to be output somewhere ... by default, both stdout and stderr are output to the terminal / screen.

How will sending large amounts of information to dev//null affect the performance of the computer?

Most likely, yes, although not significantly, for the better, the system will not have to output this information somewhere else (for example, to a hard disk or terminal / screen), thus, in theory, the performance will increase slightly.

Answer 2

Don't forget - in order to send something to dev-null, you must first read it.
the speed of receiving in null is practically unlimited, so all resources will be spent on reading data.

Answer 3

I still do not understand the meaning of the great abyss
Usually used in scripts. For example, a command is executed that, in the course of execution, makes detailed non- switchable diagnostics - you need to display it somewhere, so they merge it into / dev / null
If you need to open the file and immediately close it, for example - again in scripts
Comparison with recycler is incorrect. In Windows, by the way, there is also a NUL device - and you can copy to it :) They are used for the same purposes - for example, to check the disk for readability - you need to read it, but in order not to copy the data, they are simply copied to NUL