Written on 2018-07-09
After an internal meeting last week we decided we are going to backport select features of Halcyon 6.4 to our current mainline. The fact is that there are a few reasons that may delay a 6.4 release:First and most important is the numerous edge cases with older CMS's that we still need to take care.Secondly we will be offline (Summer vacation) between the 10th and 30th of August (Our technical support will be 24/7/365 as always).
Our original plan was to have the engine detect the version of the CMS and apply filters on demand but this adds complexity which means we may not be able to release on time. Thus we decided we will be backporting some features we think are extremely important for performance of specific payloads.
One of the payloads that will get a big boost in performance is media heavy apps, in our internal testing we have on average a 38% boost in delivery of the content. which is the difference between a 3.6s to 1.4s page delivery.
Last Thursday(2018/07/05) we started pushing the release to all of our servers and since Saturday(2018/07/07) every site is been served using the latest version.
We will still try to hit our target for an August release.
Best Regards,George PantaziseSGR CTO
Fun Fact: On 2018/07/03 03:19:41 UTC+3 Freca served the 10.000.000.000.000th http request since eSGR was incorporated in 2009.
Written on 2018-06-18
Written on 2018-03-20
Written on 2018-03-15
Written on 2018-03-06
Written on 2018-01-24
Written on 2018-01-17
Written on 2018-01-11
Written on 2018-01-09
The recent Intel cpu bugs resulted in us doing a hardware overhaul of most of our infrastructure. Unfortunately the cpu bugs didnt only lower the security of our infrastructure but also dropped the performance significantly.
DB Cluster:On all of our services we always work with a cpu margin of 20% that is used in emergencies or temporary expansion. On our DB cluster the aggregate of all nodes meant we had 2.6 extra servers than what was needed. Our DB cluster suffered most with an average of 42% drop in performance, which in essence meant we needed an extra 3 servers to even cope with the current requirements.
Solution:We added 3x new AMD EPYC 7401P 24/48 in the cluster that provides the same core count as 12x Xeon E5 6/12 and 75% more performance in computing power. The new cluster of only 3x new servers is at 47% load on average. We will be adding another server in mid-2018 just to increase redundancy and another one as planned in mid-2019.Status: DB Cluster Is fully functional and ready.
VPS:In the summer of 2017 (2017/08/09) we switched all of our nodes from Xeon E5 6/12 to EPYC 7401P in a rate of 3:1. That was done purely for performance reasons, at the same time we completely elliminated magnetic storage on our VPS service and lowered the prices dramatically.
Status: VPS Service is fully functional and ready.
In our original schedule we would have started upgrading our platform mid-2019 but the Intel bug has forced us to expedite the process. We switched all Xeon E5 dual socket servers (effective 12/24 per server) to EPYC 7601 (effective 64/128 per server), the RAM was upgraded from 128GB to 256GB. Finally we moved our hybrid shared hosting to pure SSD hosting. With this change we quintupled our cores thus octupling our computing power, doubled our memory capacity, quadrupled our disk bandwidth and octupled our iops capacity.Status: We are in the process of starting the move of all accounts to their new home.We will update with more information on the the bugs and mitigation issues.Regards,eSG NOC
Written on 2018-07-10
Written on 2018-07-07
Written on 2018-07-06
Written on 2018-04-04
Written on 2018-03-14
Written on 2018-03-12
Written on 2018-02-16