I'll take a look into that and see if it has any relevance, is that issue a solid v.1.4 + Smartermail 17 specific issue?
We've run solidcp for along time now and if the issue was prevalent in version 1.4.3 then we would have seen the same performance issues in smartermail 16, prior to the upgrade a month or so ago.
Or on the flip side, the Solid issue was there but better code in version 16 meant less of an impact on overall performance of all services.
Tony, my stats are showing the complete opposite of what you are claiming. What metrics are you using to monitor performance, have you tweaked your servers to run with similar or better performance to previous versions, are you testing in the real world, how are you monitoring and testing? Simply stating that your product is fast doesnt mean its fast, give me something to work with and back the statement.
The info I posted is factual, its data gathered from our monitoring and the logs dont lie.
Below are two screenshots of response times for POP services, clearly there is an issue, and you can see it starts immediately after upgrading.
I have two important tickets waiting at the moment and none of them are being attended to as your developers are busy with MAPI - so I doubt that logging a support ticket now will get anything resolved until MAPI is rolled out, and after that we'll have to wait for those bugs to be ironed out.
Alex's issue is very different to ours, we are running our smartermail servers on Enterprise Grade SuperMicro Servers with SSD's for OS, separate SSD's for the spool, separate SSD's for logging, separate enterprise grade hard drive for archiving, and separate Enterprise grade hard drive for mail files.
Each our servers are equipped with ECC ram + dual XEON E5 v4 CPU's.
I would entertain the idea that the performance we are seeing on our servers was isolated if 1 or 2 of these four servers were experiencing slow performance, but all four are behaving in the same manner.