Nice step by step guide to identify on which layer do you have an issue : Physical, Data Link, Network/Internet or Transport?
This blog post explains how computers running the Linux kernel receive packets, as well as how to monitor and tune each component of the networking stack as packets flow from the network toward userland programs.
The Utilization Saturation and Errors (USE) Method is a methodology for analyzing the performance of any system. It directs the construction of a checklist, which for server analysis can be used for quickly identifying resource bottlenecks or errors. It begins by posing questions, and then seeks answers, instead of beginning with given metrics (partial answers) and trying to work backwards.
The USE Method can be summarized as:
For every resource, check utilization, saturation, and errors.
On the same website:
EvE online is also home to a expansive world map to hold all of these players. At its peak EvE had 63,000 players online in a single world with 500,000 paying subscriptions on top, and while that number is getting lower by the year the world remains infamously large. Meaning that to get from one side to another is a sizable amount of time (and risk due to player owned factions).
You travel to different areas using warping (within the same system) or jumping to different systems using a jump gate
What would a EvE online internet of systems look like?
we operate Kubernetes as follows to try and minimise it:
- We run multiple production clusters and teams are able to choose which clusters to run their application in. We don’t use Federation yet (we’re waiting on AWS support) but we use Envoy instead to load-balance across the different cluster Ingress load-balancers. We can automate much of this with our Continuous Delivery pipeline (we use Drone) and other AWS services.
- All clusters are configured with the same Namespaces. These map approximately 1:1 with teams.
- We use RBAC to control access to Namespaces. All access is authenticated and authorised against our corporate identity in Active Directory.
- Clusters are auto-scaled and we do as much as we can to optimise node start-up time.
- Applications auto-scale using application-level metrics exported from Prometheus.
Top 2 performers are bjoern (written in C) > meinheld (based on picoev)
-
"Ansible is simple, which is a major strength", it "works by connecting to a server using SSH, copies the Python code over, executes it and then removes itself".
"Ansible Tower is the Enterprise version, it turns the command line Ansible into a service, with a web interface, scheduler and notification system."
"you can’t have long-running tasks." -
"StackStorm is designed as a highly-configurable if-this-then-that service. it can react to events and then run a simple command or a complex workflow."
"MongoDB can be scaled using well-documented patterns." "StackStorm extensibility system is a key strength." "If StackStorm were a programming language, it would be strongly typed." -
"Salt was born as a distributed remote execution system used to execute commands and query data on remote nodes."
"Ultra high-performance for large deployments." (LinkedIn use it)
GNU Mailman
Mailjet, la solution tout-en-un pour envoyer et délivrer vos emails marketing et transactionnels à partir d’un même compte.
Monitoring NGINX, part 1 of 3. This post introduces the key NGINX metrics you can monitor to detect performance issues in your web infrastructure.
server-configs - Boilerplate configurations for various web servers.