[Advice] Be careful when adding tons of files or deep directory structures to your file system if your NVMe SSD slot is below the CPU

This page summarizes the projects mentioned and recommended in the original post on /r/kde

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • crates.io-index

    Registry index for crates.io

  • But the aggravating factor was Baloo, I've been seeing Baloo very busy those days, I have very deep directories in my file system and I've also cloned a repo with a fairly deep directory structure days ago, but Baloo wasn't causing overheat to my SSD, until today, it looks like Baloo found some deep directory structure in my disk and went crazy on indexing, once the notification appeared, I opened iotop and Baloo Read Throughput was 500Mbps up to 1Gbps, this is not bad, but SSDs tend to overheat easily on sustained reads/writes, and Baloo was doing this for a long time.

  • fd

    A simple, fast and user-friendly alternative to 'find'

  • For searching I commonly use fd-find, which is pretty fast, indexing is not really needed in SSDs.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • tokei

    Count your code, quickly.

  • However, considering File Content Indexing is enabled, I should look at how much text data it has to index, so I did it, I used tokei to count the LOCs of my development directories, these are the results: ```

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts