Currently dolphin's trash system feels incredibly sluggish by default on manydistributions. I feel this has a negative impact on a lot of new users -- andpotentially unknowing experienced users -- in regards to their feeling aboutdolphin and KDE in general.

I think this situation could be remedied a couple of different ways:- Switch defaults so that dolphin operates on a 30 day time frame cleanup,rather than a disk %- Change the limiting system to be handed by a background job; so effectivelywhen you delete a file, it would be immediately moved, but then in thebackground, something would be tasked with cleanup the necessary amount of diskspace from the trash soon after. This would allow the user to get instantfeedback, and the enforcement of the disk space limit would then happenseamlessly in the background, without any impact to user experience.

--You are receiving this mail because:You are watching all bug changes.

Post by Wyatt ChildersCurrently dolphin's trash system feels incredibly sluggish by default onmany distributions. I feel this has a negative impact on a lot of new users-- and potentially unknowing experienced users -- in regards to theirfeeling about dolphin and KDE in general.- Switch defaults so that dolphin operates on a 30 day time frame cleanup,rather than a disk %- Change the limiting system to be handed by a background job; soeffectively when you delete a file, it would be immediately moved, but thenin the background, something would be tasked with cleanup the necessaryamount of disk space from the trash soon after. This would allow the user toget instant feedback, and the enforcement of the disk space limit would thenhappen seamlessly in the background, without any impact to user experience.

Actually upon further testing, it seems the time based trash enforcement issubject to the same performance penalties, and could benefit from the proposedchanges to disk space limiting.

--You are receiving this mail because:You are watching all bug changes.

--- Comment #4 from Alexander Meshcheryakov <***@gmail.com> ---I noticed this too. In my case deleting files had several seconds delay, butsubsequent deletion was instantaneous. I suppose delay is caused by calculationof current trash size to decide whether it needs cleaning before adding newcontent. While trash contents listing is cached in OS, it takes way less timeto recalculate occupied space for next deletion, but once it gets squeezed outof cache moving content to trash needs to reread disk content.

One more thing that corroborates this theory: recently calculation of occupiedspace got broken in my system ( https://bugs.kde.org/show_bug.cgi?id=383324#c2), now dolphin shows free space of trash equal to its size limit regardless ofcontents. And now moving content to trash is always instantaneous for me.

If my assumption is correct, this bug should not be noticeable for users withtrash on SSD. My $HOME is located on HDD, so reading thousands of files/dirs oftrash listing from storage should take seconds.

Wyatt, Huon are your trash located on HDD or SSD?

--You are receiving this mail because:You are watching all bug changes.

Post by Alexander MeshcheryakovI noticed this too. In my case deleting files had several seconds delay, butsubsequent deletion was instantaneous. I suppose delay is caused bycalculation of current trash size to decide whether it needs cleaning beforeadding new content. While trash contents listing is cached in OS, it takesway less time to recalculate occupied space for next deletion, but once itgets squeezed out of cache moving content to trash needs to reread diskcontent.One more thing that corroborates this theory: recently calculation ofoccupied space got broken in my system (https://bugs.kde.org/show_bug.cgi?id=383324#c2 ), now dolphin shows freespace of trash equal to its size limit regardless of contents. And nowmoving content to trash is always instantaneous for me.If my assumption is correct, this bug should not be noticeable for userswith trash on SSD. My $HOME is located on HDD, so reading thousands offiles/dirs of trash listing from storage should take seconds.Wyatt, Huon are your trash located on HDD or SSD?

BTRFS SSD here

--You are receiving this mail because:You are watching all bug changes.