Hello. I've decided to share a lot more of my knowledge in public forums from now on, and to not divert any of my focus away from improving the world in a way that stays written in history.
This Gist is about discussing on how to improve AV1 decoding performance on 2 fronts: improving performance through more efficient decoding, and through decoding aware encoding.
Here are many tips on how to improve decoding performance on any machine:
Out of the box, my SMB performance on macOS 12.3.1 would top out at around 20MB/s in short ~5 second bursts, which was absolutely horrendous, slow to navigate in Finder and slugish to interact with.
Since making these changes, I now get sustained ~80-100MB/s+ and instant Finder navigation which is superb and how things should be out-of-the-box (OOTB)!
May 2023 update: As of Ventura, the SMB issues were just horribly inconsistent and hard to maintain. Something in the combination of Unraid, macOS and SMB just doesn't play nice. I ended up binning NFS/SMB all together and heading to a locally hosted Nextcloud instance for file syncing, then using SFTP/Ansible Git flow for editing files within appdata.
The core of most real-time fluid simulators, like the one in EmberGen, are based on the "Stable Fluids" algorithm by Jos Stam, which to my knowledge was first presented at SIGGRAPH '99. This is a post about one part of this algorithm that's often underestimated: Projection
The Stable Fluids algorithm solves a subset of the famous "Navier Stokes equations", which describe how fluids interact and move. In particular, it typically solves what's called the "incompressible Euler equations", where viscous forces are often ignored.
| parameters: | |
| - name: Value | |
| type: boolean | |
| default: true | |
| pool: | |
| vmImage: ubuntu-latest | |
| stages: |
| // branded types to allow for better type inference | |
| // with default generic types | |
| /* eslint-disable @typescript-eslint/naming-convention */ | |
| type NO_PAYLOAD = { | |
| JgJES6BF8uyaOwF1: "FY7eBhPYJlqOxuVp"; | |
| }; | |
| type OPTIONAL_PAYLOAD = { | |
| A7nWdXs0r5RLuHRf: "zPcrRNRIl4r5IHbA"; | |
| }; |
NOTE: Content below is written by Adrian Mace. Click here for an updated version.
Below are the key settings that I apply on any unifi installation for optimal performance.
Enable Advanced Features is enabled
| import * as playwright from 'playwright'; | |
| /** | |
| * Defines type used to extract complex values from the page. | |
| */ | |
| type CompositeSelector = { | |
| selector?: string; | |
| attributeName?: string; | |
| } |
| import * as fs from 'fs'; | |
| import { resolve } from 'path'; | |
| import { promisify } from 'util'; | |
| import yargs from 'yargs'; | |
| const exists = promisify(fs.exists); | |
| const readFile = promisify(fs.readFile); | |
| const writeFile = promisify(fs.writeFile); | |
| const root = resolve(__dirname, '..', '..'); |
I'm writing this as my notes on hardening a Kali Linux system running kernel version 5.6.14. This is by no means an exhaustive list of everything that could be done
This is meant for general-purpose, daily-use Linux laptop. Most notably, this is a one-user system. I'm the only user here, so countermeasures for user-infighting are not taken here. I also do a lot of programming (and debugging), so some features such as the kernel Yama module are not turned to their most restrictive settings.
I'm skipping pre- and during-install procedures, such as disk encryption, secure boot, etc.. You should start this process with an already-completed fully-encrypted, passworded install. I'm also assuming some very basic knowledge, such as what constitutes a strong password, and how to edit files.
Almost all of these changes require a reboot to take effect. I'm leaving out how to apply changes on-the-fly here, but expect to reboot after major changes. The etckeeper package may be help
If you're using a high-end bluetooth headset on your Macbook Pro it's likely your mac is using an audio codec which favors battery efficiency over high quality. This results in a drastic degradation of sound, the SBC codec is the likely culprit, read more about it here.
