reflections on OSS, HPC, and Ai/ML engineering, with occasional considerations on Cognitive Neuroscience
02:42, awoken to first-morning, 4hrs sleep 02:55, at home office standing desk 02:58, navigate to eBay once more 02:59, search Sparc M7 T7-2 chassis 03:08, begin writing silly poem 03:12, resume eBay search 03:16, distracted by dtrace for tcshrc 03:20, distracted by view of Lake Michigan 03:22, return to Mastodon post-form 03:28, distracted by tcsh config options 03:32, review
Data-At-Rest Encryption is a common topic, but one which is often misunderstood. Having led engineering and architectural efforts involved with hardware standards for encryption compliance, including detailed analysis of performance impacts while operating in accordance to service level agreements, here are some bits of discussion on the SED/Opal implementation. TL;DR * SED/Opal TCG spec'd drives are doing just fine. I trust it more than LUKS2 by
See that image? Right around the mid-section we see a common problem with the manner in which code is shipped to production. That one little section, displayed as a subsection of "build & packaging", happily named "regression + performance testing". Whether the product is a user-facing site, or middle-ware component, or baremetal systems which provide cloud resources that we all know and (sometimes) love... the success of
Test post. The variable value specifies the vicissitudes of vectorized validity of variablities.