BleachBit and SSD Drives


I am a new user of this forum and I have a question.

is it a good idea to use BleachBit with an Opperating System which resides on a SSD drive (in my case a Samsung 830 256 GB).

If e.g. Window 7 resides on a SSD, it is modified in such a way, that the write requests are minimized,
because write operations are blamed to reduce the lifetime of the SSD.

I reconized, that BleachBit e.g removes a lot of data in the USER DATA and PROGRAM DATA folders.
I asume, that a lot of this entries are rebuilt, as soon as the related programs are used again.
This means, that BleachBit increases the write accesses to the SSD significantly.

Is it therefore adviseable to not use BleachBit for SSD's and let the entries just exist, even if a significant amount of storage (in may case I could save 2.5 GB which is only about 1 % of my 256 GB SSD) could be saved.

What is the oppinion of the developers.
Could it be a good idea to check the disk type before removind and erasing specific entries.


It depends on the circumstances, and here are some general answers.

If the user is neither immediately concerned about privacy nor disk space, then do not use BleachBit. If a backup is done monthly, then run BleachBit once a month before a backup. If disk space becomes critically low or usage patterns change (for example, switching between browsers), run BleachBit then. If privacy is always a concern, then run BleachBit often, and the cost of privacy will be a shorter life of the SSD.

Andrew, lead developer