If you are big into password management apps like #KeePass then you can take full advantage of the security of the database by configuring your key derivation settings.

KeePass 2.x supports databases encrypted with AES and ChaCha20 and key derivation with AES-KDF or Argon2. Argon2 is designed to be especially resistant to brute forcing which makes it tougher on ASICs, GPUs and memory when performing the derivation. This means to get a similar amount of speed of attempts in a second they would need to have far more expensive resources in comparison to other functions.

Argon2d and Argon2id are options in KeePassDX, but Argon2id is generally recommended.

In #KeePassDX you can go to Settings -> Security -> Key derivation function to use Argon2 in your database.

A good configuration is the default. However if you want to be overkill, then you could make the effort to make it take about 1 second or more to save the database or unlock it. It's up to you to configure these values and go up slowly. Try to keep memory and parallelism around the same as the defaults.

Sadly KeePassDX doesn't have an option to calculate how many iterations it can perform in a second unlike the original KeePass2 on Windows or other apps.

In my example my Pixel 6a uses 80 transformation rounds, 32MiB memory and 4 threads parallelism.

#m=image%2Fjpeg&dim=1080x1149&blurhash=%7B34ef%40%25M9FM%7BIUM%7BRjs%3A%7EWt7D%25V%40WBWBRjfkt8jZRjfkt7j%5BWVbHIUt7xuRjj%5BWBjYoL4noK%25Ma%7Dt7WVa%7DWV9FWBxuoft7j%5BofaeIUR*ofofofoft6jZt7RPV%40t7ayt7oza%7DxuRjWBs%3ARjt7ofjZ&x=a70e6f2192b07569e92fc2f43995f406ad0c7356bd490f0341d3fc8f0bcb32e8

#m=image%2Fjpeg&dim=1080x1411&blurhash=_24B%3F%5E_4t7IUITIUIU%25NRjRjWBoft7j%5BxvRjayofkCj%5BWB.8ofRPM%7Bfkt7of%25MWBRjRjoft7j%5BtRayjsayaea%7Dj%5Bt7ayayayfkj%5Ba%7Dxuxut7fkRjRjRjjZs%3At7j%5DWBWBay&x=3b4e9220e0a23ec90a6832d4bfcc9ce2ed85680fd703334bdb8003b9a2a9832d