About the disk rate limit I meant.... because the user is awaiting and as it's a big amount of data... a user wouldn't mind to wait... so... there perhaps we could.... slow down a little for prioritizing other users faster tasks.... -------- Mensaje Original --------
Good morning, We are suffering some performance issues with some new ssd disks we are testing. We suffer in performance, due to write amplification and trims. Having seen that, I have been thinking perhaps a couple of things would be very useful in Cyrus. We use delete mode delayed and that's nice for messages, but does not help when you remove for instance one big folder with 50.000 messages each. I say it because for that purpose Cyrus creates the entire hierarhy under DELETED again. When say it creates I mean it copies first whole deleted folders, then deletes them from original place. One extremely nice thing that Cyrus has, is the possibility of removing content at cyr_expire running time... nightly... it's a big pity not to be able to do this same with a whole deleted folder. I think that perhaps a new folder/mailbox state could be created for avoid listing that folder in a LIST or LSUB.... Later cyr_expire to check the existence of folders in that state (folder removed) and then to be removed (but at night... when cyr_expire runs...). Another idea, I think it would be very useful is, when a non admin user is copying a very big amount of data, to be possible to rate limit the total amount of disk io at which that copy could be done. I think that could be extremely useful too. If is nothing similar created (of both things) do you think too could be useful?. I could try to propose to my bosses working on it and later to share this work with Cyrus community :) . What do you think about it?. Cheers, |
