Howard Chu @ Symas<p>I've dedicated most of my career to writing the most efficient code.</p><p><a href="https://ngmx.com/@mejofi/114889780968597360" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ngmx.com/@mejofi/1148897809685</span><span class="invisible">97360</span></a></p><p>But the mention of storing way more data than you're ever going to use also triggered me here.</p><p>It's a common symptom of poorly designed apps looking for write-optimized databases like RocksDB. If your workload is more write heavy than read, then by definition you're writing more than you'll use.</p><p>It's another reason why <a href="https://mastodon.social/tags/LMDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LMDB</span></a> is read optimized, because we only care about data we'll actually use.</p>