Has anyone else noticed that if a user deletes a number of GB of mail spanning several thousands emails that it can kill SmarterMail performance? In this scenario it was 6GB covering perhaps 10,000 messages and actioned via webmail. Both RAM and CPU go through the roof for an hour or more.

I saw this a number of versions back (perhaps v15) but have not encountered it again until today. The server normally idles, <10% CPU and circa 25% RAM usage. I am not sure if it is the IO of the move or if the move triggers re-indexing and then 'barfs' .

We are running the last but one build and as noted we saw it in earlier versions. This feels like a combination of an issue triggered by the move (reindexing?) which is compounded by the fact that the user activity is not constrained. On that note I presume there is no concept of throttling within SmarterMail to limit the fallout any one user can cause? - Perhaps a feature request as Microsoft deploy it widely within Exchange online to prevent one user impacting others (EWS throttling comes to mind but I believe it is employed to more than one protocol)