In accordance with the European law, we inform you that this shop uses cookies to secure the ordering process, observe the customer traffic to improve our website/offer. For more information, You can consult our privacy policy in our TOS.
We went around, everything is ok now a priori, do not hesitate to let us know any problem on the site ...
Update
Our test on PHP 7 works after having corrected a dozen modules, remains 1-2 tinkers, so we will stay in PHP7 hoping to see stability and no issues. We gained a bit of loading time on admin side and site, we can not do better :)
Hello, Sata3 disks still have a performance problem despite all recent optimizations, it's time to upgrade to higher technologies with 100% SSD, so that to avois these small slowdowns which appear from tim to time due to IOPS limit of Sata disks. The new generation SSD is also twice more efficient as the SSD that is currently used. We will switch from Tier3 to Tier 4 (network redundancy in addition) The server will have the hot swap, and a dual power supplyLifespan of this new server : 2024Everybody will be migrated with no pain on your side, and no price changes for anyone Estimated date of migration : february 10-20 thSee you soon,JohannCEO YOORshop
Hello, For sometimes, we were asking ourselves who was due to micro-slowdowns on the server which translate into an IOwait spike, and we decided to conclude it 4 days ago by mobilizing external experts ... Yesterday, by ourselves, we found the key to undo with the observed logs log, the problem occurs every second 5-6-7-8 every time, so we thought about the cron ... Is a fact that the service cron of the server provided by centos lacks something, ie it executes the cron of the server at the same second whatever the minute, and the cycle of the cron, and it is in The case of a powerful server, even in SSD, and with quite a lot of users ... After consulting the experts on a solution, the first proposed is a good solution, and it is not certain at this stage that there is another: insert in cron this:Sleep $ (expr $ RANDOM \% 30); This dilutes the execution of the cron on one second at random the first 30 seconds ... As a result, we have modified the visible cron directly in the server's cron files (others are not visible because managed inside the CMS) We have updated accordingly the article on the cron so that out user tries to do as recommended ...
