# storage Published articles for storage. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## TrueNAS Releases Native Proxmox VE Storage Plugin for iSCSI and NVMe/TCP DevFeed: [TrueNAS Releases Native Proxmox VE Storage Plugin for iSCSI and NVMe/TCP]() Original publisher: [Read original article]() Author: Lyle Smith Published: 2026-09-17T16:19:04Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [truenas](), [Proxmox](), [NVMe](), [systems](), [Authentication]() Tags: [enterprise](), [plugin](), [proxmox](), [snapshot](), [software](), [storage](), [truenas](), [vm]() ### AI overview TrueNAS released a native Proxmox VE storage plugin that provisions and manages VM disks as OpenZFS zvols on TrueNAS 25.10 or later. The plugin supports iSCSI and NVMe/TCP storage transports and lets administrators manage disk creation, snapshots, resizing, migration, and deletion from Proxmox. ### Source excerpt TrueNAS has released a native Proxmox VE storage plugin that lets Proxmox provision and manage VM disks directly on TrueNAS systems. A disk requested in Proxmox becomes an OpenZFS zvol on TrueNAS 25.10 or later, published as an iSCSI LUN or an NVMe/TCP namespace, and the plugin handles creation, snapshots, resizing, migration, and deletion from The post TrueNAS Proxmox Plugin Turns Every VM Disk Request Into an Automated zvol Over iSCSI or NVMe/TCP appeared first on StorageReview.com. ## Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions DevFeed: [Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions]() Original publisher: [Read original article]() Author: Nispriha Jagan; Neeraj Krishna Gopalakrishna Published: 2026-09-16T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Security](), [mount](), [Filesystems](), [chmod](), [Unix]() Tags: [chmod](), [container](), [containers](), [filesystem](), [hardening](), [kubernetes](), [linux](), [mount](), [permissions](), [storage](), [volume](), [volumes]() ### AI overview Kubernetes v1.37 adds bind mount options and emptyDir permission modes to strengthen storage security. The article explains how noexec, nosuid, nodev, Unix permissions, and the sticky bit can help enforce security policies on writable volumes. ### Source excerpt Kubernetes v1.37 brings important storage security features: emptyDir permission modes and bind mount options. They help application programmers and security professionals implement rigorous security policies, for example, prohibiting deletion of files across containers or execution of arbitrary binaries from writable volumes, directly in Kubernetes without any complicated circumvention. Linux storage and permission fundamentals Before diving into the new Kubernetes features, let us briefly review the low-level Linux security mechanisms that make them possible. Bind mount flags When Linux mounts or remounts a directory, Virtual File System (VFS) flags control what actions are permitted on that filesystem: noexec: Do not permit direct execution of any binaries on the mounted filesystem. nosuid: Do not allow set-user-identifier or set-group-identifier bits to take effect. nodev: Do not interpret character or block special devices on the file system. Directory permissions and the sticky bit Standard Unix permissions regulate access across three scopes: Owner, Group, and Others (e.g., 0755 or 0777). Beyond standard read, write, and execute bits, Linux supports the sticky bit (as in mode 01777). When applied to a directory, the sticky bit ensures that a file inside that directory can only be deleted or renamed by the file's owner or root. This is essential for shared writable directories like /tmp. Motivation for the improvements Why does Kubernetes need bind mount options and emptyDir permissions? The primary goal of these features is to increase the security of Kubernetes workloads by allowing security-related bind mount options on volume mounts. By default, volumes are bind-mounted into containers by the container runtime and kubelet without noexec, nosuid, or nodev flags. This default can undermine security. For example, with noexec missing, a compromised process can use any writable volume (emptyDir, PersistentVolume, etc.) to download, chmod +x, and execute arbitra ## Hobby projects now retain fewer deployments to free up storage DevFeed: [Hobby projects now retain fewer deployments to free up storage]() Original publisher: [Read original article]() Author: Pranav Kanchi Published: 2026-09-16T18:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Deployment](), [Disk image]() Tags: [3](), [deployments](), [retention](), [storage](), [upgrade]() ### AI overview Vercel has changed Deployment Retention for Hobby teams. Each Hobby project now keeps its three most recent production deployments and three most recent deployments of any type, while some protected deployments remain exempt. Deployments outside the exceptions are deleted immediately when a team exceeds the 10GB storage limit. ### Source excerpt Hobby projects now retain fewer deployments past the 30-day retention window. Hobby teams get 10GB of Deployment Storage. Every deployment you keep uses some of it, and going over the limit can block you from deploying until you free some up. Deployment Retention for Hobby teams now deletes old deployments sooner, so dormant projects stop holding storage that your active projects need. Each Hobby project now keeps its 3 most recent production deployments, plus its 3 most recent deployments of any type, regardless of age. Preview deployments no longer get their own protection. Your current production deployment is still never deleted, and aliased and active-branch deployments are still protected. See the full list of exceptions in the docs. If your team is over the 10GB limit, deployments outside those exceptions are now deleted immediately instead of after 30 days. To stay under the limit, see how to optimize your Deployment Storage usage, or upgrade to Pro, where storage is billed at $0.10 per GB per month. Read more ## Why Kafka retention.ms can delay message deletion DevFeed: [Why Kafka retention.ms can delay message deletion]() Original publisher: [Read original article]() Author: Rogerio Santos Published: 2026-09-16T13:05:06Z Content type: tutorial Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [Kafka](), [Apache-Kafka](), [configuration](), [file](), [Event-Streaming]() Tags: [broker](), [configuration](), [diagnose](), [event-driven](), [how-to](), [kafka](), [lifecycle](), [retention](), [storage](), [stream-processing]() ### AI overview This guide explains why Kafka messages can remain readable beyond a topic's retention.ms setting. Kafka deletes closed log segments rather than individual messages, and the active segment and continuous writes can delay removal of older records. ### Source excerpt A customer opened a support case with a deceptively simple complaint: a Kafka topic was configured with a 12-hour retention (retention.ms), yet messages produced on July 24 were still readable 4 days later, on July 28. Nothing was broken. The broker logged no errors. The retention policy was working as designed, but the segment layout and continuous write pattern delayed when the old records could actually be removed. The post Why your Kafka topic ignores retention.ms (and how to fix it) appeared first on Red Hat Developer. ## Dropbox Outlines How Focusing on Existing Infrastructure Efficiency Can Create Headroom for AI DevFeed: [Dropbox Outlines How Focusing on Existing Infrastructure Efficiency Can Create Headroom for AI]() Original publisher: [Read original article]() Author: Matt Foster Published: 2026-09-16T07:15:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Artificial Intelligence](), [cloud-infrastructure](), [Magic Pocket](), [data centers](), [networking]() Tags: [ai](), [ai-architecture](), [ai-ml-data-engineering](), [capacity](), [cloud](), [data-center](), [data-storage](), [devops](), [dropbox](), [dropbox-datacenter](), [efficiency](), [infrastructure](), [infrastructure-optimisation](), [magic-pocket](), [ml-data-engineering](), [networking](), [news](), [optimization](), [storage](), [sustainable-computing]() ### AI overview Dropbox describes how long-running infrastructure optimization helps it accommodate growing AI demand by improving forecasting, fleet utilization, storage density, hardware lifecycles, and rack-level power delivery. Its storage infrastructure has used more than 50% less power per petabyte since 2020. ### Source excerpt Dropbox has outlined how a decade of infrastructure optimization is helping it absorb growing demand from AI without treating new data-center capacity as the only answer. Its work spans forecasting, fleet utilization, storage density, hardware lifecycles, and rack-level power delivery, much of it predating the current AI boom. By Matt Foster ## Mercure Broadcasting in Laravel 13.32 DevFeed: [Mercure Broadcasting in Laravel 13.32]() Original publisher: [Read original article]() Author: Paul Redmond Published: 2026-09-16T02:44:52Z Content type: release Language: en Sources: [Laravel]() Topics: [Laravel](), [releases](), [Release notes](), [real-time](), [enum](), [WebSocket]() Tags: [enums](), [features](), [github](), [laravel](), [laravel-releases](), [news](), [queue](), [real-time](), [release](), [release-notes](), [storage](), [update](), [websockets]() ### AI overview Laravel 13.32 adds a Mercure broadcast driver, filesystem methods for copying and moving files between disks, and enum support for queue pause and resume methods. The release also includes additional fixes and updates. ### Source excerpt Laravel 13.32 adds a Mercure broadcast driver, Storage::copyToDisk() and moveToDisk(), enum support in queue pause/resume, and more. The post Mercure Broadcasting in Laravel 13.32 appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## Seagate and WD AI Storage Research Finds Enterprises Rank Storage Above Compute as the AI Bottleneck DevFeed: [Seagate and WD AI Storage Research Finds Enterprises Rank Storage Above Compute as the AI Bottleneck]() Original publisher: [Read original article]() Author: Lyle Smith Published: 2026-09-15T17:23:54Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [Data Infrastructure](), [AI Infrastructure](), [idc](), [Inference](), [Retrieval-Augmented Generation](), [synthetic-data]() Tags: [ai](), [compute](), [data-infrastructure](), [datasets](), [enterprise](), [genai](), [hdd](), [idc](), [inference](), [reports](), [research](), [retrieval](), [storage](), [synthetic-data]() ### AI overview Seagate and WD published separate studies indicating that AI is increasing enterprise storage requirements and extending data retention. Although their headline percentages differ because they asked different questions, both reports point to storage becoming a larger part of AI infrastructure planning alongside growing archive and retrieval needs. ### Source excerpt Seagate and WD published separate AI storage studies within days of each other; the headline numbers: Seagate says 99% of enterprises expect AI to increase their storage requirements over the next three years, while WD's IDC research puts the comparable figure at 74%. Read the fine print, and both reports land in the same directional The post Seagate and WD AI Storage Research Finds Enterprises Rank Storage Above Compute as the AI Bottleneck appeared first on StorageReview.com. ## OWC Acquires OpenDrives, Adding Atlas, Astraeus, and Edge to the Jellyfish Shared Storage Line DevFeed: [OWC Acquires OpenDrives, Adding Atlas, Astraeus, and Edge to the Jellyfish Shared Storage Line]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-15T16:55:08Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [data-architecture](), [cloud-infrastructure](), [Hardware](), [data-processing]() Tags: [acquisition](), [cloud-native](), [company](), [enterprise](), [enterprise-storage](), [hybrid-cloud](), [infrastructure](), [products](), [storage]() ### AI overview Other World Computing (OWC) has acquired OpenDrives, bringing the Atlas, Astraeus, and Edge platforms into its Jellyfish shared storage portfolio. The companies say the deal expands OWC's capabilities in enterprise data management, hybrid cloud orchestration, and edge workflows; financial terms were not disclosed. ### Source excerpt Other World Computing (OWC) has acquired OpenDrives, the Los Angeles software-defined storage company whose Atlas platform has sat behind Hollywood studios, post houses, and live broadcast networks since 2011. The deal brings OpenDrives' Atlas, Astraeus, and Edge platforms into OWC's shared storage portfolio alongside the Jellyfish line, and OWC says it extends that line into The post OWC Acquires OpenDrives, Adding Atlas, Astraeus, and Edge to the Jellyfish Shared Storage Line appeared first on StorageReview.com. ## Kubernetes 1.36 restores a lost guarantee for database backups DevFeed: [Kubernetes 1.36 restores a lost guarantee for database backups]() Original publisher: [Read original article]() Author: Shubham Pampattiwar Published: 2026-09-15T13:00:00Z Content type: news Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack](), [The New Stack]() Topics: [Kubernetes](), [PostgreSQL](), [Databases]() Tags: [backups](), [cncf](), [consistency](), [database](), [databases](), [kubernetes](), [post-contributed](), [postgresql](), [snapshots](), [sponsor-cncf](), [sponsored-post-contributed](), [stateful](), [storage]() ### AI overview The article explains how Kubernetes 1.36 restores coordinated snapshots for applications whose state spans multiple volumes, addressing inconsistent database backups caused by taking individual PersistentVolumeClaim snapshots at different times. ### Source excerpt It's 2 a.m., and you're restoring a PostgreSQL cluster from last night's backup. Its data directory lives on one PersistentVolumeClaim The post Kubernetes 1.36 restores a lost guarantee for database backups appeared first on The New Stack. ## Just 4.4% of Enterprise NAS Capacity Is Active, CTERA Cold Data Storage Report Finds DevFeed: [Just 4.4% of Enterprise NAS Capacity Is Active, CTERA Cold Data Storage Report Finds]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-15T12:00:00Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [data](), [Filesystems](), [Security](), [Replication](), [Artificial Intelligence]() Tags: [data](), [enterprise](), [enterprise-nas](), [enterprise-storage](), [nas](), [report](), [security](), [storage]() ### AI overview StorageReview reports on CTERA's Cold Data Storage Report, which analyzed 16 petabytes of production data from 856 enterprise NAS file-share discovery scans. The report found that 4.4% of stored capacity was actively used within 90 days, while most files were cold or inactive. The article discusses the resulting storage, data-protection, security, and AI-retrieval implications. ### Source excerpt CTERA has published The Cold Data Storage Report, an analysis of 16 petabytes of live production data across 856 file-share discovery scans in enterprise NAS environments, including regulated industries, and the headline number is that just 4.4% of stored capacity is actively used, which the report page defines as modified within a 90-day window. The The post Just 4.4% of Enterprise NAS Capacity Is Active, CTERA Cold Data Storage Report Finds appeared first on StorageReview.com. ## How Solaris' Turnstile Influenced the Modern System Designs of Web Browsers and Language Runtimes DevFeed: [How Solaris' Turnstile Influenced the Modern System Designs of Web Browsers and Language Runtimes]() Original publisher: [Read original article]() Author: Olimpiu Pop Published: 2026-09-15T06:06:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [systems](), [Programming](), [Kernel](), [observability](), [browsers](), [web browsers]() Tags: [architecture](), [architecture-design](), [architectures](), [blocking](), [concurrency](), [development](), [efficiency](), [kernel](), [locking](), [memory](), [news](), [observability](), [operating-systems](), [solaris](), [storage](), [systems](), [turnstile-system-design]() ### AI overview The article examines how Solaris innovations influenced modern systems engineering. It discusses the Slab Allocator, OpenZFS, DTrace, Zones, and turnstiles, focusing on how turnstiles reduce per-lock memory overhead while supporting priority inheritance for contended locks. ### Source excerpt Sun's Solaris influenced modern systems engineering, with key innovations like the Slab Allocator for efficient memory management, OpenZFS for advanced storage, and DTrace for observability. Its turnstile mechanism addressed issues with mutexes, promoting lean locking designs that are reflected in contemporary programming languages and web browsers, enhancing performance and memory efficiency. By Olimpiu Pop ## Kubernetes Changed Block Tracking API - Beta Differences DevFeed: [Kubernetes Changed Block Tracking API - Beta Differences]() Original publisher: [Read original article]() Author: Prasad Ghangal Published: 2026-09-14T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [API](), [gRPC]() Tags: [2026](), [compatibility](), [container-image-registry](), [developer](), [documentation](), [kubernetes](), [registry](), [release](), [snapshots](), [storage](), [streaming](), [update]() ### AI overview This Kubernetes developer article explains the Beta changes to Changed Block Tracking (CBT) support for CSI drivers. The SnapshotMetadataService CRD moved from v1alpha1 to v1beta1, with no automatic conversion, and CBT remains limited to block volumes. It also outlines compatibility requirements and the steps for upgrading and trying the feature. ### Source excerpt Changed Block Tracking (CBT) support for CSI drivers shipped as Alpha in September 2025. With the March 2026 v1.0.0 release of the external-snapshot-metadata project, the feature moved to Beta. If you aren't yet familiar with changed block tracking for storage in Kubernetes, the Alpha announcement covers the motivation, the three primary components (the CSI SnapshotMetadata gRPC service, the SnapshotMetadataService CRD, and the external-snapshot-metadata sidecar), and a walkthrough of how to use the API. CBT currently applies to block volumes; file-volume and network file-share changed-list tracking is not covered by this feature. This post focuses on what is different in Beta. What's new in Beta The main change in that release was the promotion of the SnapshotMetadataService CRD from v1alpha1 to v1beta1. The CRD used to advertise a driver's metadata service now serves cbt.storage.k8s.io/v1beta1. The schema itself is unchanged, but this release removed v1alpha1 (rather than serving it alongside the new version). If you are upgrading from Alpha, you need to: Re-apply the CRD definition shipped with v1.0.0. Update SnapshotMetadataService manifests to use apiVersion: cbt.storage.k8s.io/v1beta1. Update any client or controller code that talks to the CRD. This is a one-time change. There is no automatic conversion between the two versions. Compatibility Minimum Kubernetes version: 1.33 CSI spec: 1.10 or newer Container image: registry.k8s.io/sig-storage/csi-snapshot-metadata:v1.0.0 Trying it out The Getting Started section in the Alpha blog still applies. In short: Make sure your CSI driver supports volume snapshots and ships the external-snapshot-metadata sidecar. Install the SnapshotMetadataService CRD (the v1beta1 definition from the v1.0.0 release). Create a SnapshotMetadataService resource for your driver. Use a client -- snapshot-metadata-lister, or your own implementation -- to call GetMetadataAllocated and GetMetadataDelta. If you want to see the full flow end-to-e ## You Don't Need a VR-Ready PC (or a PC at all) to Use Steam Frame DevFeed: [You Don't Need a VR-Ready PC (or a PC at all) to Use Steam Frame]() Original publisher: [Read original article]() Author: Scott Hayden Published: 2026-09-14T16:59:00Z Content type: opinion Language: en Sources: [Road to VR]() Topics: [pc](), [Linux](), [Streaming]() Tags: [bluetooth](), [games](), [linux](), [pc](), [pc-vr-news-reviews](), [storage](), [streaming](), [wi-fi](), [xr-industry-news]() ### AI overview The article argues that Steam Frame can function as a standalone VR and gaming device, without requiring a VR-ready PC or any PC at all. It provides a self-contained setup, Steam interface, Linux desktop, access to flat and VR games, Bluetooth peripheral support, and expandable storage. ### Source excerpt Valve essentially considers Steam Frame a 'streaming-first' VR device, capable of directly connecting to your PC via a Wi-Fi 6E dongle so you can play high-quality VR and flatscreen games. But don't let the RAMpocalypse get you down: you don't even need a PC, VR-ready or otherwise. Before I ever got my hands on Frame, [...] The post You Don't Need a VR-Ready PC (or a PC at all) to Use Steam Frame appeared first on Road to VR. ## Speeding Up Azure Durable Functions with Fan-Out/Fan-In and a Higher Concurrency Limit DevFeed: [Speeding Up Azure Durable Functions with Fan-Out/Fan-In and a Higher Concurrency Limit]() Original publisher: [Read original article]() Author: Michael Li Published: 2026-09-14T12:00:32Z Content type: tutorial Language: en Sources: [Atomic Object]() Topics: [Azure](), [Concurrent Programming](), [Code]() Tags: [apis](), [azure](), [azure-functions](), [batch](), [concurrency](), [development-practices](), [file](), [storage]() ### AI overview An Azure Durable Functions batch job was accelerated by combining fan-out/fan-in orchestration with a higher function-host concurrency limit. Together, the changes reduced a representative run from about 710 seconds to about 240 seconds. ### Source excerpt For one of our projects, we run a nightly job that generates a batch of files. It's a long process: pulling records from an upstream system, calling several APIs to gather info about each one, generating a file per record, and writing the results back to storage. For a small batch, this works fine, but [...] The post 2 Changes Made Our Azure Durable Functions 3X Faster appeared first on Atomic Spin. ## A Case Study: Building an EN 18031-Compliant IoT Solution with ESP32-C5 and ESP RainMaker DevFeed: [A Case Study: Building an EN 18031-Compliant IoT Solution with ESP32-C5 and ESP RainMaker]() Original publisher: [Read original article]() Author: John Lee Published: 2026-09-14T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Internet of things](), [Security](), [Cloud](), [Security & Privacy](), [Espressif](), [Authentication](), [Authorization]() Tags: [access-control](), [authentication](), [blog](), [compliance](), [connectivity](), [cryptographic](), [data](), [data-management](), [documentation](), [en-18031](), [esp-rainmaker](), [esp32-c5](), [espressif](), [eu](), [firmware](), [iot](), [privacy](), [rainmaker](), [regulatory](), [security](), [standards](), [storage]() ### AI overview This case study describes an ESP32-C5 and ESP RainMaker device-to-cloud IoT implementation assessed against EN 18031 cybersecurity and privacy requirements for products targeting the EU market. ### Source excerpt This case study assesses device-to-cloud IoT implementation of products based on ESP32-C5 and ESP RainMaker against the EN 18031 security requirements for the EU market. ## Cloudflare Tests Cache Transcoding to Reduce Storage Requirements DevFeed: [Cloudflare Tests Cache Transcoding to Reduce Storage Requirements]() Original publisher: [Read original article]() Author: Renato Losio Published: 2026-09-13T10:35:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Caching](), [Transcodings](), [cloud-infrastructure](), [Pingora]() Tags: [architecture-design](), [cache](), [caching](), [cdn](), [cloud](), [cloudflare](), [cloudflare-cache-transcoding](), [compression](), [cpu](), [data-centers](), [development](), [edge-computing](), [news](), [pingora](), [rust](), [storage]() ### AI overview Cloudflare is testing Cache Transcoding, a prototype that Zstandard-compresses eligible uncompressed text before it is stored in cache. The approach aims to increase effective cache capacity and reduce inter-data-center transfer, with configurable CPU and storage trade-offs. ### Source excerpt Cloudflare recently described a prototype called Cache Transcoding that compresses eligible cache content, mainly uncompressed text such as HTML, JSON, CSS, and JavaScript, using Zstandard before storing it on disk. The hyperscaler estimates that the approach could provide petabytes of additional effective cache capacity, although broader testing is still needed. By Renato Losio ## Linux server performance: Is disk I/O slowing your application? DevFeed: [Linux server performance: Is disk I/O slowing your application?]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-09-12T16:11:54Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [IO](), [Server](), [Command-line interface](), [Processes](), [NVMe]() Tags: [blog](), [command-line](), [cpu](), [linux](), [load](), [mysql](), [nvme](), [performance](), [processes](), [request](), [server](), [ssd](), [storage](), [sysadmins](), [terminal]() ### AI overview This tutorial explains how disk I/O bottlenecks can cause high Linux load averages even when CPU usage is low. It shows how to use top, atop, and iotop on a LEMP web server, including per-core I/O wait measurements, to identify storage-related application slowdowns. ### Source excerpt If your Linux server is bogged down by disk I/O, your first step may often be to use the top command in the terminal to check load averages. Continue reading... ## A Humorous List of Physical Alternatives to GitHub for Storing Projects DevFeed: [A Humorous List of Physical Alternatives to GitHub for Storing Projects]() Original publisher: [Read original article]() Author: Sulaiman Bah Published: 2026-09-12T12:00:11Z Content type: opinion Language: en Sources: [Atomic Object]() Topics: [GitHub](), [datacenter](), [RAID](), [USB]() Tags: [data-center](), [github](), [project-team-management](), [raid](), [storage](), [the-software-life](), [usb](), [version-control]() ### AI overview This humorous commentary proposes physical storage options as alternatives to GitHub, including a homemade 50-petabyte data center, a 64-gigabyte USB stick, and a 2-terabyte external hard drive. ### Source excerpt Every developer knows just how important it is to share work with a coworker. If you are working on a critical feature in a crunch, prompt peer reviews and instant feedback can mean the difference between a secure contract and an angry client. So it follows that when the infrastructure we rely on to work [...] The post GitHub Alternative List: Quintessential Options appeared first on Atomic Spin. ## How we shipped 15 Tbps for OpenAI in 90 days (Session 2 of 3) DevFeed: [How we shipped 15 Tbps for OpenAI in 90 days (Session 2 of 3)]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-09-12T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [OpenAI](), [Network](), [GPU](), [Server](), [Cache](), [API](), [Oracle Database]() Tags: [api](), [architecture](), [build](), [cache](), [capacity](), [database](), [debugging](), [execution](), [gateway](), [gpu](), [network](), [object](), [openai](), [performance](), [platform-engineering](), [server](), [servers](), [sre](), [storage](), [testing](), [warp]() ### AI overview The second session describes turning an architecture for OpenAI's 15 Tbps system into a delivery plan. It covers coordinated capacity planning across network, gateway, server, storage, and database teams; caching object names through the Inventory API; delivery tracking; and performance validation. Early WARP testing found packet drops caused by an unsuitable MTU of 1500, which was changed to 9100. ### Source excerpt Architecture was only the first week. Session 2 is about the build: capacity, execution discipline, and the first signs that performance would be the real test. ## Kubernetes v1.37: Native Histograms Graduates to Beta DevFeed: [Kubernetes v1.37: Native Histograms Graduates to Beta]() Original publisher: [Read original article]() Author: Richa Banker Published: 2026-09-11T18:30:00Z Content type: release Language: en Sources: [Kubernetes Blog]() Topics: [telemetry]() Tags: [kubernetes](), [latency](), [metrics](), [observability](), [prometheus](), [storage](), [telemetry](), [time-series]() ### AI overview Kubernetes v1.37 enables Prometheus native histograms by default at Beta. The article explains how dynamic exponential buckets improve metric resolution and quantile accuracy while reducing time-series, scraping, and storage overhead compared with classic histograms. ### Source excerpt I'm excited to announce that native histogram support for Kubernetes metrics is graduating to Beta and is enabled by default in Kubernetes v1.37! Native histograms (previously introduced as Alpha in Kubernetes v1.36 under KEP-5808) bring high-resolution, low-cardinality observability to Kubernetes metrics. By adopting Prometheus Native Histograms, Kubernetes components now expose latency and duration metrics with far greater accuracy while significantly reducing telemetry storage and scraping overhead. Why move beyond classic histograms? Since the early days of Kubernetes observability, duration and latency metrics (such as API server request latencies or scheduling durations) have relied on classic Prometheus histograms. Classic histograms require metric authors to define a static list of cumulative bucket boundaries (le labels), such as 0.005, 0.01, 0.025, 0.05, 0.1, 0.25, 0.5, 1, 2.5, 5, 10. While familiar, this approach introduces three major challenges: The Bucket Guessing Game: If a workload's latency profile changes, for example, shifting into microsecond ranges or experiencing long-tail tail latencies beyond the highest bucket, the histogram loses visibility. Specifying bucket boundaries upfront requires knowing the distribution before observing it High Cardinality & Storage Cost: With classic histograms, each bucket boundary is exported as a separate time series (_bucket{le="..."}). A histogram with 10 buckets across multiple labels multiplies the number of time series by 10, increasing memory consumption in Prometheus and inflating time series database (TSDB) storage costs Interpolation Error in Quantiles: Calculating percentiles using histogram_quantile() relies on linear interpolation between static bucket boundaries. When bucket spans are coarse, quantile calculations can suffer from significant estimation error What are Prometheus native histograms? Prometheus Native Histograms replace static user-defined buckets with dynamic, exponential buckets. Inst ## Building a reliable cloud native foundation for distributed AI training DevFeed: [Building a reliable cloud native foundation for distributed AI training]() Original publisher: [Read original article]() Author: Abhi Kulkarni and Shishir Jindal, Atlassian Published: 2026-09-11T11:00:00Z Content type: article Language: en Sources: [Cloud Native Computing Foundation]() Topics: [Training AI Models](), [Machine learning](), [distributed-systems](), [GPU](), [cloud-infrastructure](), [Network design](), [Inference]() Tags: [ai-training](), [blog](), [distributed-training](), [gpu](), [infrastructure](), [storage]() ### AI overview The article explains how to make multi-node AI training reliable by treating inter-node communication, shared storage, hardware placement, network topology, and validation as platform concerns. It identifies RDMA for GPU-node communication and Lustre for concurrent training-data and checkpoint access. ### Source excerpt AI workloads are changing what platform teams need from infrastructure. Provisioning GPUs and standing up a cluster no longer makes a platform "AI-ready." Once training spans more than one node, the bottlenecks show up in places... ## Rapidly scaling online storage to serve over 1 billion ChatGPT users DevFeed: [Rapidly scaling online storage to serve over 1 billion ChatGPT users]() Original publisher: [Read original article]() Published: 2026-09-11T10:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [cloud-infrastructure](), [Database](), [data]() Tags: [chatgpt](), [data](), [database](), [engineering](), [global](), [infrastructure](), [openai](), [platform](), [python](), [scale](), [storage]() ### AI overview OpenAI describes scaling Habitat from a Python client-side library into a distributed online storage platform for global product traffic. The article focuses on reliability, performance, and capacity decisions made during rapid growth. ### Source excerpt Learn how OpenAI evolved Habitat from a Python library into a globally distributed storage platform serving 1 billion ChatGPT users and 22M requests per second. ## fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound DevFeed: [fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-11T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [container](), [mount](), [Security](), [Process]() Tags: [container](), [container-image](), [kubernetes](), [mount](), [network](), [performance](), [reliability](), [security](), [stateful](), [storage](), [waiting]() ### AI overview This article explains why a stateful pod can remain in ContainerCreating for fifteen minutes when fsGroup triggers a recursive chown across a large network-backed volume. It describes how fsGroupChangePolicy: OnRootMismatch can skip the recursive walk when the volume root group already matches, and discusses the setgid invariant that supports this behavior. ### Source excerpt Pod stuck in ContainerCreating from fsGroup recursive chown: fsGroupChangePolicy: OnRootMismatch, and why the setgid bit on the volume root makes it safe. ## Vercel Sandbox now provides 64 GB of storage DevFeed: [Vercel Sandbox now provides 64 GB of storage]() Original publisher: [Read original article]() Author: Luke Phillips-Sheard Published: 2026-09-11T06:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel]() Tags: [agent](), [dependencies](), [documentation](), [sandbox](), [sandboxes](), [storage](), [vercel]() ### AI overview Vercel Sandbox storage has increased from 32 GB to 64 GB for all sandboxes, including those created from managed or custom images and those using the deprecated runtime property. ### Source excerpt Every Vercel Sandbox now includes 64 GB of storage, up from 32 GB. This includes sandboxes created from a Vercel Managed Image or custom image, as well as those configured with the deprecated runtime property. The additional space provides more room for large repositories, dependencies, build artifacts, data workloads that spill to disk, and storage-intensive agent tasks. Learn more about Sandbox images in the documentation. Read more [Next page]()