- Install fish via Brew
- Optionally install Oh My Fish!
- Add fish to known shells
- Set default shell to fish
brew install fish
curl -L https://get.oh-my.fish | fishbrew install fish
curl -L https://get.oh-my.fish | fish| $INPUTVIDEO='input.mp4' | |
| $OUTPUTVIDEO='output.mp4' | |
| ffmpeg -i $INPUTVIDEO -metadata:s:v rotate="-90" -codec copy $OUTPUTVIDEO |
| function Save-KBFile { | |
| <# | |
| .SYNOPSIS | |
| Downloads patches from Microsoft | |
| .DESCRIPTION | |
| Downloads patches from Microsoft | |
| .PARAMETER Name | |
| The KB name or number. For example, KB4057119 or 4057119. |
By default Linux distros are unoptimized in terms of I/O latency. So, here are some tips to improve that.
Most apps still don't do multi-threaded I/O access, so it's a thread-per-app which makes per-app speed always bottlenecked by single-core CPU performance (that's not even accounting for stuttering on contention between multiple processes), so even with NVMe capable of 3-6 GB/s of linear read you may get only 1-2 GB/s with ideal settings and 50-150/100-400 MB/s of un/buffered random read (what apps actually use in real life) is the best you can hope for.
All writes are heavily buffered on 3 layers (OS' RAM cache, device's RAM cache, device's SLC-like on-NAND cache), so it's difficult to get real or stable numbers but writes are largelly irrelevant for system's responsiveness, so they may be sacrificed for better random reads.
The performance can be checked by:
| #!/usr/bin/env bash | |
| # Show info and run flatpak apps with fzf | |
| # flatapp [arguments] | |
| flatpak_preview() { | |
| app="$(echo "${1}" | awk -F'\t' '{print $2}')" | |
| flatpak info "${app}" | |
| } | |
| export -f flatpak_preview |
| param( | |
| $OutDir = ".", | |
| [ValidateSet("x64", "x86", "arm64")] | |
| $Arch = "x64" | |
| ) | |
| if (!(Test-Path $OutDir)) { | |
| $null = mkdir $OutDir | |
| } |