fleet
microprocessor-trend-data
Our great sponsors
| fleet | microprocessor-trend-data | |
|---|---|---|
| 5 | 5 | |
| 2,438 | 463 | |
| - | - | |
| 0.0 | 1.8 | |
| - | about 2 years ago | |
| Go | Gnuplot | |
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fleet
-
The 2024 Web Hosting Report
Docker didn’t have a default way to run on multiple hosts, and so in the wake of docker’s explosive adoption there was a rush of different solutions offered for scheduling containers across a fleet. One of the first well-adopted solutions was actually called fleet - it was part of CoreOS, whose team went on to be very influential throughout the container revolution. This was in the systemd era, and was basically seen as a multi-host systemd. It was very cool and it worked great!
-
The Container Orchestrator Landscape
Figure out how to revive https://github.com/coreos/fleet as something native in systemd?
-
Kubernetes is just Systemd distributed just like /etc is ETCD(istributed)
I guess what in trying to say is k8s is systemd distributed but more then. I see how in line fleet and systemd is though https://github.com/coreos/fleet/blob/master/Documentation/fleet-k8s-compared.md
-
We Don’t Use Docker (We Don’t Need It)
What you describe is essentially the original CoreOS fleet[0] project. It's distributed systemd init files.
[0] https://github.com/coreos/fleet#fleet---a-distributed-init-s...
I find it ironic half of k8s mojo, etcd, came out of this project as well.
microprocessor-trend-data
-
We Don’t Use Docker (We Don’t Need It)
Clock speed != single-threaded performance. Clock speeds plateaued a long time ago, single threaded performance is still improving exponentially (by being able to execute multiple instructions in an instruction stream in parallel, as well as execute the same instructions in less clock cycles), though the exponent approximately halved around 2004 (if the trend had continued we would be at about a 100x improvement by now).
Hard to say it's still "exponential"...what do you think the current constant doubling period is now?
Here's the single thread raw data from that repo. If you take into account clock speed increase (which, as you agree, have plateaued) we're looking at maybe a 2x increase in instructions per clock for conventional int (not vectorized) workloads.
Is there even another 2x IPC increase possible? At any time scale?
https://github.com/karlrupp/microprocessor-trend-data/blob/m...
What are some alternatives?
confd - Manage local application configuration files using templates and data from etcd or consul
peg - Peg, Parsing Expression Grammar, is an implementation of a Packrat parser generator.
borg - Search and save shell snippets without leaving your terminal
orange-cat
croc - Easily and securely send things from one computer to another :crocodile: :package:
limetext - Open source API-compatible alternative to the text editor Sublime Text
JayDiff - A JSON diff utility
restic - Fast, secure, efficient backup program
Hugo - The world’s fastest framework for building websites.
Gor - GoReplay is an open-source tool for capturing and replaying live HTTP traffic into a test environment in order to continuously test your system with real data. It can be used to increase confidence in code deployments, configuration changes and infrastructure changes.
syncthing - Open Source Continuous File Synchronization
Comcast - Simulating shitty network connections so you can build better systems.