You can see CPU steal when using the top command. In the hypervisor world, CPU steal can be seen as the hypervisor limiting your ability to use CPU cycles. In the significantly worse cause, your provider could be overselling there hardware, and the steal is coming from your neighbours sharing the physical hardware. I noticed from the screenshot that the server was a t3.medium. The T series processes at AWS are sold as burstable instances. They are not designed to be used at max capacity. If your server only sees a high load 20% of the time, it is perfect. At SnapShooter, we make hefty use of them as our ingestion load is very busty. Most people do backups at the hour mark, so our load always peaks for 5-10minutes after every hour. Continue Read
A little bit of background. The 2nd of November was the launch of SnapShooter’s new backups engine. Now, this brought a lot of improvements to the way we do backups with databases and file systems as well as directly supporting applications. One of the most significant improvements I found was that we do real-time logging from a customers server back to SnapShooter. Unlike before where we would SSH into someone's server and pull the log periodically. This process was far more efficient; the logs would stream directly from customer servers back to SnapShooter. This was probably the biggest unknown for the launch because previously the traffic was relatively low. Server load was all dependent on the queue workers, but now we were going to be processing millions of inbound connections per day. Continue Read
You maybe have missed the news AWS created a second Linux Distribution, which is optimised to run containers. Bottlerocket is for containers and containers only! Continue Read
Stephan Müller has lead the developer of a new /dev/ramdom implementation with the 35th patch including various coe improments and fixes. Continue Read