First change since #swad 0.2 will actually be a (huge?) improvement to my #poser lib. So far, it was hardwired to use the good old #POSIX#select call. This is perfectly fine for handling around up to 100 (or at least less than 1000, YMMV) clients.
Some #select implementations offer defining the upper limit for checked file descriptors. Added support for that.
POSIX also specifies #poll, which has very similar #scalability issues, but slightly different. Added support for this as well.
And then, I went on to add support for the #Linux-specific #epoll and #BSD-specific #kqueue (#FreeBSD, #NetBSD, #OpenBSD, ...) which are both designed to *solve* any scalability issues
A little thing that slightly annoyed me about kqueue was that there's no support for temporarily changing the signal mask, so I had to do the silly dance shown in the screenshot. OTOH, it offers changing event filters and getting events in a single call, which I might try to even further optimize ...
Today at the Environment Reading Group we talked about #Scalability by reading "On #Nonscalability: The Living World Is Not Amenable to Precision-Nested Scales" by Anna Lowenhaupt Tsing.
In a nutshell: scalability is a colonial project, based on monoentities and wants to control and dominate the environment. While it will never succeed, mainly due to planetary limits, is a great capitalist vehicle for destruction.
#GitHubCopilot is the largest LLM-powered code completion service in the world. They serve hundreds of millions of requests a day with an average response time of under 200 milliseconds.
How Open Source Powers the Enterprise – Yesterday, our Commercial Director Ronny Marx took the stage at #CloudFest to share why WordPress is made for enterprise companies.
43% of all websites run on WordPress – meaning nearly every second website you visit is powered by it! He also showcased real-world cases proving that WordPress is both scalable and secure.
Kubernetes is revolutionizing AI deployment with its scalable and efficient container orchestration capabilities.
Here are the key perks: Scalability: Automatically scales AI workloads to handle surges in demand, ensuring seamless performance. Efficient Resource Management: Optimizes CPU, GPU, and memory allocation based on workload needs, reducing costs. Multi-Tenancy: Allows multiple teams to share resources without interference, enhancing collaboration. High Availability: Ensures AI applications remain operational even during hardware failures, thanks to self-healing capabilities. Seamless Deployment: Enables consistent deployment across different environments, from on-premises to cloud.
#Kubernetes in action: real-world #AI deployment success stories Kubernetes is transforming AI deployment across industries with its robust container orchestration capabilities.
Some use cases: Netflix: Uses Kubernetes to simplify and streamline deployments, ensuring resilience and scalability for its vast array of microservices. HSBC: Manages applications across private and public clouds with Kubernetes, optimizing resource costs and meeting regulatory requirements. Airbnb: Orchestrates resources for complex machine learning models, ensuring efficient processing of large datasets. YouTube: Utilizes Kubernetes for scalable video delivery, handling spikes in demand without disrupting service quality.
Kubernetes is revolutionizing how organizations manage complex applications, offering scalability, flexibility, and robustness. Here are some more key use cases: Large-Scale Apps - Kubernetes helps manage large-scale apps during peak traffic, ensuring a smooth user experience. AI/ML with Kubernetes - NVIDIA uses Kubernetes to deploy AI models at scale, optimizing resource utilization. DevOps Efficiency - Spotify speeds up software delivery with Kubernetes, reducing time to market. ...
Big question, Why ATProtocol from #BlueSkySocial#PBC’s mouth instead of Mastodon and ActivityPub?:
“Why not use ActivityPub? #ActivityPub is a federated social networking technology popularized by #Mastodon.
Account #portability is a major reason why we chose to build a separate protocol. We consider portability to be crucial because it protects #users from sudden bans, server shutdowns, and policy disagreements. Our #solution for portability requires both signed data repositories and #DIDs, neither of which are easy to retrofit into ActivityPub. The migration #tools for ActivityPub are comparatively limited; they require the original server to provide a redirect and cannot migrate the user's previous data.
Another major reason is #scalability. #ActivityPub depends heavily on delivering messages between a wide network of small-to-medium sized nodes, which can cause individual #nodes to be flooded with traffic and generally struggles to provide global views of #activity.”