News for hackers. Stuff that matters.
Re:Bash 5.0 released by nerdponx on Monday January 07, 2019 @10:56PM (#18853013)
What is the value in creating built-in replacements for binaries like rm and stat?
Re:Bash 5.0 released by steventhedev on Tuesday January 08, 2019 @02:02AM (#18853854)
My guess is that it's less about performance so much as reliability. I've had three incidents in the last two years which required connecting to a server that had an out of control process pool that had exhausted pids.

I also had a storage controller go and had to figure out how to use shell builtins to create a tmpfs and reflash the firmware.

There are many reasons to provide builtins for basic file commands, from saving the extra process start to the tiny performance boost for scripts that should probably be using find instead.

Re:Bash 5.0 released by dualbus on Monday January 07, 2019 @11:24PM (#18853132)
The built-in replacements run in the same process as the Bash shell, and thus, avoid the fork/exec system calls.

It's a minor performance optimization that might be useful if you're doing thousands of rm's or stat's in a script.

Re:Bash 5.0 released by chrisshroba on Monday January 07, 2019 @11:20PM (#18853117)
It seems like this would eliminate the need to read a file from disk and fork a new process, both of which take time. If you're just removing a single file, this is probably negligible, but if you have a script iterating over 10k files, i.e., this speed-up may be more welcome.
Re:Bash 5.0 released by viraptor on Tuesday January 08, 2019 @12:05AM (#18853316)
> if you have a script iterating over 10k files

That's probably a good sign you should advance from shell. If the script is trivial, it's going to be trivial in python / ruby / go / crystal / ... as well. If it's not trivial, that's another reason to move.

Re:Bash 5.0 released by adrianN on Tuesday January 08, 2019 @12:41AM (#18853499)
I agree that as scripts get more complex, you should migrate from bash. But the number of files a script touches says almost nothing about its complexity.
Re:Bash 5.0 released by viraptor on Tuesday January 08, 2019 @03:20AM (#18854128)
Wasn't saying otherwise. One reason is complexity. Another is performance.
Re:Bash 5.0 released by pwg on Tuesday January 08, 2019 @06:40AM (#18854853)
True, but if you are iterating over 10k files and removing them, then a find|xargs pipe with xargs feeding rm the maximum number of parameters the kernel allows per fork will likely be faster than a bash interpreter loop, even with a bash builtin rm.
Re:Bash 5.0 released by e12e on Tuesday January 08, 2019 @02:19PM (#18858613)
You think find|xargs would be faster than (gnu) find -delete?
Re:Bash 5.0 released by pwg on Tuesday January 08, 2019 @04:31PM (#18859902)
No, my comment was "will likely be faster than a bash interpreter loop". The key phrase is "bash interpreter loop".

I was not comparing find|xargs to find -delete.

Re:Bash 5.0 released by orev on Monday January 07, 2019 @11:26PM (#18853142)
It’s faster to run them as a builtin than to exec the external binary. It makes a big difference when looping over many items.