We have one report of 100% CPU.  Every other speed related ticket etc. has been how fast it is and how much we reduced startup times etc.  We just got a ticket in for a customer who had a 5 minute startup time and with the new release he is at 25 seconds.  If you have any concerns, please contact support.  We are doing no new work and all employees are focused on looking at ANY and ALL tickets.  If an issue or issues do arise, all resources are available.

There have been some smaller fixes and we will be releasing Builds pretty regularly.  Build 6913 was released last night.

mine is lightning fast ...

No issue in terms of speed on our server either. 

Fabulously quick here too

I was just updated on the customer with the 100% CPU issue.  The was the result of an unusually large greylisting file so this issue wouldn't affect most customers.  We have already resolved the issue and it will be available in the next Build which will probably be on Friday.

Well, maybe its related to the size of mailbox data etc.  I just moved an email from inbox to a folder and it took about 20 seconds for the message to disappear under the search results I had.  I'll look into this more on our end as far as CPU and the SSD storage array.  We have about 1000Gb of mail storage usage maybe that is a difference between our systems maybe not, could any of you share the mail storage size and what you are running it on?  Our server is running on a ZEN host in a cluster and has been assigned 12Gb of RAM and 8 cores from CPU.  I am also going to investigate whether it is still indexing.  i can say that yesterday we went from build 6911 to 6913 and it was much faster in general than when I started this post, but searching and moving emails still seems real slow compared to the previous major version running last week.  I'll keep looking and reviewing this thread, thanks for your time in responding and feedback.

Yea, you are probably still indexing the mailboxes on the server.  The upgrade requires everything to be re-indexed because we have a significantly newer and faster indexing system.  Indexing is at a very low priority to ensure all other activity on the server is at full speed.

Ok, I have a bit more info and another question.  First, it appears slow only when i search a folder (searching isn't fast) and then the results are listed (lets say my search is the word "west").  Now with those results I highlight and delete a single email in the results list, it takes about 10 seconds or so.  If I take one of the messages from the results and move it to a folder, it takes longer, maybe 15 seconds.  I see the memory usage spike on the server more than double normal usage when I perform either of these operations from web interface on client.   Question I have is how can I determine if the storage is still being indexed?  Thanks

We have noticed a slowdown when searching in conjunction with some actions on messages etc. It has been escalated and will be resolved early next week.  Those actions will be optimized.  It will not cause any issues on the server itself.

Ditto for us, our upgrade now as the CPU pegged at 100% using Friday's build. Hasnt left 100% for almost 2 hours now. Thought maybe it was the indexing, changed the max threads to 1, seems to be no difference between 1 and 16.