Measure pipe throughput in the shell
There is a shell command that allows you to measure how fast the data goes through it, so you can measure the speed of output of commands in a pipe. So instead of:
There is a shell command that allows you to measure how fast the data goes through it, so you can measure the speed of output of commands in a pipe. So instead of:
I realized I can use a window manager without a desktop environment and don’t lose any functionality I care about. Applications still work fine, I can still arrange application windows as I please. This pretty much eliminates the need for lightweight desktop environments such as LXDE and XFCE for use cases like mine. I wonder … Read more
I tend to use pipelines in my bash scripts over process substitution in most situations, especially in cases of using multiple sets of commands as it seems more readable to do ... | ... | ... over ... < <(... < <(...)).
I have directory with cca 26 000 files and I need to grep in all these files. Problem is, that I need it as fast as possible, so it’s not ideal to make script where grep will take name of one file from find command and write matches to file. Before “arguments list too long” issue it took cca 2 minutes to grep in all this files.
Any ideas how to do it?
edit: there is a script that is making new files all the time, so it’s not possible to put all files to different dirs.
Are there any specific recommendations on speeding up X applications over ssh on a slow network connection? In this specific case, I am accessing a server located in west coast from a laptop in east coast and that too on a not too fast DSL connection.
I always thought that the only benefit of using dash instead of bash was that dash was smaller, and therefore many instances of dash would start faster at boot time.
I was wondering if there are general guidelines for optimizing Bash scripts.
I am considering using btrfs on my data drive so that I can use snapper, or something like snapper, to take time based snapshots. I believe this will let me browse old versions of my data. This would be in addition to my current off site backup since a drive failure would wipe out the data and the snapshots.
Is there a diagram that shows how the various performance tools such as ip, netstat, perf, top, ps, etc. interact with the various subsystems within the Linux kernel?