microprocessor-trend-data
Data repository for my blog series on microprocessor trend data. (by karlrupp)
s6-overlay
s6 overlay for containers (includes execline, s6-linux-utils & a custom init) (by just-containers)
Our great sponsors
microprocessor-trend-data | s6-overlay | |
---|---|---|
5 | 27 | |
463 | 3,515 | |
- | 1.9% | |
1.8 | 4.6 | |
about 2 years ago | about 1 month ago | |
Gnuplot | Shell | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
microprocessor-trend-data
Posts with mentions or reviews of microprocessor-trend-data.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-03-15.
- DCS Newsletter - DCS 2.8 Multithreading | SATAL 2023
-
Semiconductor Engineering: "Chip Design Shifts As Fundamental Laws Run Out Of Steam"
And the creator of that graph has updated it: https://github.com/karlrupp/microprocessor-trend-data
-
Is it realistic at this time in the near future (aka within 5-10 years) that we could see 1000 players in a single match of Fortnite or Battlefield? What is holding this back? People's machines or the infrastructure of most countries?
I'm not familiar with how Battlefield servers are run, but I’m going to assume they are single-core processes. That’s what most game servers I’m familiar are, anyways. Two of the most important attributes of a CPU are its clock rate (the number of clock cycles per second, which is a measurement of how quickly one core can execute instructions) and its thread count (i.e. how many different processes can be executing on the CPU at the exact same time). Over the past decade, CPUs haven't gotten much faster in terms of clock rate. Instead, they've been optimized to add more cores, so that the CPU can do more tasks at once. This means that game servers haven’t been able to fully enjoy most of the improvements to CPU performance over the past decade. More on this here. This isn’t to say single core processes have been completely left behind – advances in instruction-level parallelism such as AVX 512 can certainly benefit game servers if they are leveraged correctly.
-
We Don’t Use Docker (We Don’t Need It)
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...
s6-overlay
Posts with mentions or reviews of s6-overlay.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-07.
- S6-overlay: one *thing* per Docker container
-
Backup Grafana SQLite with Litestream using s6-overlay in a container app
FROM docker.io/grafana/grafana-oss:9.5.12-ubuntu # Set USER to root escalating priviliges to perform installation of litestream and s6-overlay USER root RUN apt-get -qq update && \ apt-get -qq install -y xz-utils \ && rm -rf /var/libs/apt/lists/* # https://github.com/benbjohnson/litestream-s6-example/blob/main/Dockerfile # Download the static build of Litestream directly into the path & make it executable. ADD https://github.com/benbjohnson/litestream/releases/download/v0.3.11/litestream-v0.3.11-linux-amd64.tar.gz /tmp/litestream.tar.gz RUN tar -C / -xvzf /tmp/litestream.tar.gz ARG S6_OVERLAY_VERSION="3.1.5.0" # Download the s6-overlay for process supervision. ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-x86_64.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-x86_64.tar.xz # Copy s6 init & service definitions. COPY etc/s6-overlay /etc/s6-overlay # Copy Litestream configuration file. COPY etc/litestream.yml /etc/litestream.yml # The kill grace time is set to zero because our app handles shutdown through SIGTERM. ENV S6_KILL_GRACETIME=0 # Sync disks is enabled so that data is properly flushed. ENV S6_SYNC_DISKS=1 # Reset USER to 472 to reset the escalated privileges USER 472 # # Run the s6 init process on entry. ENTRYPOINT [ "/init" ]
-
Letme Dockerize for you | share your projects
Learn S6-Overlay that allows to have one docker container for multiple processes... make immich docker compose not a two page 8 containers long? But just one clean container with healthcheck. Convince the devs to switch to it.
-
Code-server : Awesome VS Code container on browser (Useful for Fast Cloud Deploy - Fix Corporate Issues)
Custom base docker image with S6 overlay (for more details : just-containers/s6-overlay)
-
xinetd/inetd/systemd socket services in Docker?
https://github.com/just-containers/s6-overlay can do what you need.
-
Alpine Linux is reducing dependencies on Busybox
Used s6-overlay[1] to start a lot daemons in a docker-image for demo purposes - postgres, tomcat, mysql, php-fpm, apache (don't ask why ;) - s6 worked really well and was reliable and stable - I enjoyed it very much. It was also possible to reliable pass SIGTERM to the daemons in the image for clean shutdown and it was easily possible to configure logging to stdout with a prefix. Modelling dependencies (waiting on database before starting app etc.pp) is possible via shell-scripts. It's super flexible but out of the box it's more like a collection of powerful tools not a complete package - but that's good. It's in the tradition of djb daemontools and is very unix - as in doesn't talk a lot and you better know how each part works but - and that's really cool - it's modular and simple and once you get a grip on it you can easily reason about it. systemd takes a completely different approach and also solves a kind of differnt problem - this is like small pieces of lego that compose well instead of one big chunk of glib/dbus/glibc only c-code.
1: https://github.com/just-containers/s6-overlay
-
Do Docker Containers go thru a Boot Process
Every container has some entrypoint, whether it launches a single binary, runs a "process supervisor" like s6, or does some pre-setup before running a service, like a database.
-
Docker and dedicated user
If you *really* want to make your own containers with PUID/PGID support checkout "S6-overlay" and the linuxserver "baseimage". Somewhere in the startup they end up running:
-
Docker Build Process: Archive Extract onto / (root), overwrites destination directories and contents
FROM ubuntu:20.04 ARG S6_OVERLAY_VERSION=3.1.0.1 ARG DEBIAN_FRONTEND=noninteractive ENV TZ="America/New_York" RUN apt-get update && apt-get install -y xz-utils ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-x86_64.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-x86_64.tar.xz RUN apt-get autoclean && rm -rf /tmp/* ENTRYPOINT ["/init"]
-
Starting a service in Dockerfile
Not sure about unbound or what have inside the pihole base image, you may try to run the service in foreground or use some tiny init service for that container (I just learnt that s6 may work for that, but you must be aware how it should be used)