Tech — Work — Ramblings

by Mike Kalvas

I see you're not using JavaScript (which is awesome!) on one of my pages that uses it to provide a better experience. If you see something not working right, please let me know. My site should work exactly the same without it apart from any exceptions noted here.

I use prism.min.js to do syntax highlighting. It clocks in at 23kb total in size. Since the majority of the writing I do involves coding, I personally find this to be a worthwhile trade off. If you choose to keep this disabled, rest assured, the code examples are still there, they just may have some extra whitespace and obviously no syntax highlighting.

I do no tracking at all and am a zealot about keeping my pages as small as possible. If you're reading a page of mine that transfers more than about 250kb over the wire (including my most gratuitous indulgence — fonts) I've messed up.

So, if you'd like to have a slightly richer experience, consider enabling javascript for my site and I promise your trust won't be misplaced.

202602222043 Read Locks and Cache Line Ping Pong

#microblog #link

I just read a great, quick article about the unintuitive times when using read locks (e.g., RwLock) in read-heavy workloads of performance critical hot paths actually perform much worse than write locks (e.g., Mutex). While this article doesn’t go too deep on the subject, it’s a good reminder to always profile performance optimizations since the results can surprise you. The article is called Read Locks Are Not Your Friends, check it out!

Links to this note

202208270000 Microblog