# Disk Space Published articles for Disk Space. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Too many GCache Page Files in MySQL Data Directory DevFeed: [Too many GCache Page Files in MySQL Data Directory]() Original publisher: [Read original article]() Author: Kedar Vaijanapurkar Published: 2026-09-17T05:29:14Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [XtraDB Cluster (PXC)](), [Replication](), [Transactions](), [MySQL]() Tags: [cluster](), [database-administration](), [disk-space](), [galera](), [galera-replication](), [gcache](), [gcache-freeze-purge-at-seqno](), [gcache-keep-pages-count](), [gcache-page](), [gcache-page-files](), [gcache-purge](), [gcache-troubleshooting](), [mysql](), [mysql-disk-space](), [mysql-troubleshooting](), [percona-xtradb-cluster](), [pxc](), [replication](), [xtradb-cluster-pxc]() ### AI overview An investigation into thousands of GCache page files accumulating in a Percona XtraDB Cluster data directory. The article explains how frozen GCache purging caused disk growth, links the behavior to a cluster partition, and describes reproducing it by setting gcache.freeze_purge_at_seqno and generating workload. ### Source excerpt Learn why PXC accumulates thousands of gcache.page.* files, how frozen GCache purging causes disk growth, and how to safely recover and rejoin using IST. The post Too many GCache Page Files in MySQL Data Directory appeared first on Percona. ## August 2026 Updates #2 for XCP-ng 8.3 LTS DevFeed: [August 2026 Updates #2 for XCP-ng 8.3 LTS]() Original publisher: [Read original article]() Author: Samuel Verschelde Published: 2026-08-27T14:03:02Z Content type: article Language: en Sources: [XCP-ng Blog]() Topics: [migration](), [Disk image](), [Kubernetes]() Tags: [2026](), [bug](), [bug-fixes](), [disk-space](), [kubernetes](), [lts](), [migration](), [storage](), [update](), [updates]() ### AI overview This article announces cumulative maintenance updates for XCP-ng 8.3 LTS. The release fixes storage-management bugs, including QCOW2 leaf-coalesce failures and LVM metadata corruption, and improves sparse QCOW2 virtual disk migration by reducing transfers and preserving VDI tags. ### Source excerpt New updates published: bug fixes related to storage management. ## Tips for Saving Game Data in Godot DevFeed: [Tips for Saving Game Data in Godot]() Original publisher: [Read original article]() Published: 2026-08-21T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Godot](), [saving](), [Concurrent Programming](), [data](), [JSON](), [Hardware](), [Testing]() Tags: [bug](), [code](), [disk-space](), [game](), [games](), [json](), [mutex](), [os](), [saving](), [testing](), [thread](), [tips]() ### AI overview This tutorial describes a save-data approach for Godot games, based on experience shipping two games. It compares custom binary and JSON formats, recommends frequent debounced saves on a separate thread, checks available disk space, and discusses temporary-file replacement to reduce corrupted save-game reports. ### Source excerpt Saving game data is easy. Making your save code survive every kind of hardware failure is not. A lot of these issues will never show up during testing, but if your game reaches a wide audience with many different kinds of hard drives in different states of degradation, you will start to get bug reports about save games not working. I decided to write up my approach, learned over the course of shipping two Godot games, that has reduced our corrupted save game bug reports to virtually nothing. ## Experiment in reducing target directory size on nightly DevFeed: [Experiment in reducing target directory size on nightly]() Original publisher: [Read original article]() Author: Jakub Beránek Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Inside Rust Blog]() Topics: [Rust](), [Compiler](), [data]() Tags: [compilation](), [compiler](), [disk-space](), [information](), [rust](), [space](), [state]() ### AI overview The Cargo Team is testing -Zembed-metadata=no by enabling it by default on the nightly channel. The experiment aims to reduce Rust target directory size by avoiding duplicated crate metadata in build artifacts, while gathering feedback about viability and user impact. ### Source excerpt TL;DR: The Cargo Team will be rolling out an experiment to identify user impact for a proposed change. Cargo will enable the -Zembed-metadata=no feature on the nightly channel by default, which can help reduce the size of the target directory somewhat. This is an experiment designed to gather feedback about viability of this feature. Users are not expected to migrate to support this feature, but to report any issues and opt-out if needed in the meantime. What is this about? High disk usage of Rust compilation artifacts is frequently cited as one of the biggest annoyances of Rust users. In our 2025 State of Rust survey, it was actually the second most commonly reported problem, right after compilation speed. There are various reasons why the target directory can become quite large, such as: Cargo compiles the whole crate graph from scratch by default, which produces a lot of build artifacts. Debug information takes a lot of disk space. Incremental compilation artifacts take a lot of disk space. While you can disable debug information or incremental compilation to reduce the target directory size, that of course comes with severe trade-offs in compilation speed and debuggability of your program. However, there is one source of data in the target directory that currently takes too much size even though it doesn't really have to. It is the "crate metadata", which can be duplicated across multiple files. We will focus on that in this blog post. What causes duplicated (meta)data For years, Cargo has been using pipelined compilation to speed up building of crate graphs. When compiling a library crate, it tells the compiler to produce an .rmeta file (which contains all the crate metadata required to use this library) as soon as possible, even before having the final executable code available. This enables dependent crates to start compiling sooner. However, once the library does finish compiling, the final produced .rlib file will contain both the executable code and the Ru ## How to free up Xcode disk space safely with an AI Agent DevFeed: [How to free up Xcode disk space safely with an AI Agent]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-07-27T08:34:16Z Content type: tutorial Language: en Sources: [SwiftLee]() Topics: [Xcode](), [AI Agent](), [Agent Skill](), [Open Source]() Tags: [agent-skill](), [agent-skills](), [ai-agent](), [ai-development](), [derived-data](), [developer-tools](), [disk-space](), [how-to](), [open-source](), [workflow](), [xcode]() ### AI overview This tutorial explains why Xcode can consume substantial disk space, especially when multiple AI agents use separate Git worktrees. It introduces an open-source Xcode Disk Cleanup Agent Skill that searches common storage locations and requires explicit approval before deleting anything. ### Source excerpt Xcode disk space can grow rapidly without you noticing. Especially these days, with multiple agents turning multiple worktrees into silent disk space occupiers. Where I used to only focus on deleting old Simulators every now and then, I'm now also actively managing worktrees and derived data folders. There are great Mac apps and open-source projects ... -> The post How to free up Xcode disk space safely with an AI Agent appeared first on SwiftLee. ## Linux Server Health Checks: 10 Metrics Every Sysadmin Should Monitor DevFeed: [Linux Server Health Checks: 10 Metrics Every Sysadmin Should Monitor]() Original publisher: [Read original article]() Author: Sujitha Paduchuri, ManageEngine Published: 2026-07-06T12:13:41Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [Monitoring](), [Linux performance](), [health checks]() Tags: [blog](), [cpu](), [disk-space](), [guests](), [health-checks](), [linux](), [linux-performance](), [load](), [memory](), [metrics](), [monitoring](), [observability](), [performance](), [performance-monitoring](), [server](), [sysadmins]() ### AI overview A practical guide to monitoring Linux server health through metrics that can reveal resource problems earlier than broad CPU, memory, or disk-usage figures. It discusses iowait, load average, active swap activity, and inode exhaustion, along with warning signs and follow-up investigations. ### Source excerpt Servers give you warnings before they fail. Most sysadmins performing Linux server monitoring miss them because they're watching the wrong numbers. The metrics that actually matter are one level deeper: iowait instead of CPU percentage, active swap paging instead of memory usage, inode counts instead of just disk space. Continue reading... ## Running out of Disk Space in Production DevFeed: [Running out of Disk Space in Production]() Original publisher: [Read original article]() Published: 2026-04-01T00:00:00Z Content type: article Language: en Sources: [Romes' Musings]() Topics: [Nix](), [Server](), [clickhouse](), [Grafana](), [nginx](), [Haskell]() Tags: [analytics](), [disk-space](), [logs](), [production](), [reverse-proxy](), [storage]() ### AI overview An incident report about a small NixOS server running out of disk space after a surge of customers downloaded large Kanjideck files. The author investigates full-disk errors, identifies Plausible Analytics and the Nix store as major consumers, and tries clearing logs, the Nix store, and ClickHouse tables; the supplied excerpt ends while space is still being consumed. ### Source excerpt Last night I put up a simple server which allowed customers to download the digital Kanjideck files. This server is hosted on a small Hetzner machine running NixOS, at 4GB of RAM and 40GB of disk space. One of these downloadable files weights 2.2GB. The matter at hand boils down to a simple Haskell program which serves static files (with some extra steps regarding authorization) plus an nginx reverse proxy which proxies requests to a certain "virtual host" to the Haskell program. Fig 1. Simplified server architecture 1 First, Panic Not even minutes after I announced that the files were finally available, hundreds of customers visited my server all at once. As the logs started flying off of my screen with all the accesses, I started noticing a particularly interesting message, repeated over and over again: Mar 31 20:43:03 mogbit kanjideck-fulfillment[2528300]: user error (Unexpected reply to: MAIL "<...> at kanjideck.com", Expected reply code: 250, Got this instead: 452 "4.3.1 Insufficient system storage\r\n") Oh no. No one's able to access their files and I'm already receiving emails about it. I messaged the users explaining the server was having some issues that I was resolving. Grafana shows 40GB/40GB disk space used up, so does df -h have 100% usage of /dev/sda. I have to clear up space fast. I'm afraid at this point that I'm not even receiving the user complaints anymore since my mail could be getting dropped by lack of space. I rushed to run du -sh on everything I could, as that's as good as I could manage. The two larger culprits were /var/lib's Plausible Analytics, with a 8.5GB (clickhouse) database, and the /nix/store with the full server configuration, installation, and executables, at 15GB. (In hindsight, I should have stopped right here to think carefully about what could possibly be occupying the remaining 20GB. I assumed "the rest of the files", but looking back the "rest of the files" could hardly total 20GB.) Delete everything that I can. First off, t ## How to Keep Staging in Sync with Production in Postgres DevFeed: [How to Keep Staging in Sync with Production in Postgres]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2025-12-23T20:42:38Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Databases](), [Replication](), [real-time](), [configuration](), [Monitoring](), [AWS Database Migration Service]() Tags: [aws](), [configuration](), [databases](), [disk-space](), [monitoring](), [postgres](), [product](), [real-time](), [replication]() ### AI overview The article compares ways to keep a PostgreSQL staging environment synchronized with production. It describes pg_dump and pg_restore as simple but slow and disruptive for larger databases, logical replication as a near-real-time option that requires manual schema and configuration management, and DMS as a managed AWS alternative with ongoing schema and configuration considerations. ### Source excerpt Staging environments drift. The fix is obvious: refresh staging from production regularly. The problem is that "regularly" and "multi-hour database copy" don't mix well. Three traditional approaches pg_dump / pg_restore This simple route works for small databases and not critical... ## Partial history expiry announcement DevFeed: [Partial history expiry announcement]() Original publisher: [Read original article]() Author: Matt Garnett Published: 2025-07-08T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Blockchain](), [data]() Tags: [announcement](), [blockchain](), [disk-space](), [ethereum](), [protocol](), [protocol-announcements](), [snap](), [space](), [storage]() ### AI overview Ethereum execution clients now support partial history expiry under EIP-4444. Removing block data from before the Merge can reduce the disk space required for an Ethereum node by 300-500 GB, while full rolling history expiry remains in development. ### Source excerpt As of today, all Ethereum execution clients support partial history expiry in accordance with EIP-4444. While work on full, rolling history expiry is ongoing, users can expect to reduce the disk space required for an Ethereum node by 300-500 GB by removing the block data prior to the Merge. This... ## Increasing GitHub Actions Disk Space DevFeed: [Increasing GitHub Actions Disk Space]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2024-11-17T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [GitHub Actions](), [Filesystems](), [Docker](), [Go Language]() Tags: [android](), [aws](), [disk-space](), [docker](), [dotnet](), [github-actions](), [go](), [haskell](), [jobs](), [nix](), [space](), [yaml]() ### AI overview The article explains why GitHub Actions workers can run out of disk space and describes removing unused preinstalled tools, Docker images, caches, and SDKs through YAML configuration. ### Source excerpt A couple of days ago, all of a sudden, my jobs started running out of space. ## Using Proxmox Backup Server to reclaim disk space and reduce backup resource usage DevFeed: [Using Proxmox Backup Server to reclaim disk space and reduce backup resource usage]() Original publisher: [Read original article]() Author: Techno Tim Published: 2024-09-28T13:00:00Z Content type: opinion Language: en Sources: [Techno Tim]() Topics: [Proxmox](), [truenas]() Tags: [disk-space](), [guide](), [homelab](), [network](), [proxmox](), [server](), [truenas]() ### AI overview The author describes switching back to Proxmox Backup Server after using NFS, reporting that the change reclaimed 6TB of disk space and reduced disk, network, and computational usage. The article also discusses storing the dataset on a TrueNAS NFS share. ### Source excerpt After years of ignoring it, I finally switched back to Proxmox Backup Server and reclaimed 6TB of disk space. Totally worth it. 📺 Watch Video Info The disk, network, and computational savings are incredible with Proxmox Backup Server and you should be using it if you are running Proxmox VE. I used NFS for years and only now do I realize how inefficient that is. This is why I started usi... ## How to uninstall packages marked "rc" on Debian / Ubuntu Linux DevFeed: [How to uninstall packages marked "rc" on Debian / Ubuntu Linux]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-05-22T09:30:57Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [apt](), [Debian](), [Ubuntu](), [configuration](), [Bash](), [Command-line interface]() Tags: [apt](), [awk](), [config](), [debian](), [debian-linux](), [disk-space](), [easy](), [grep-command](), [how-to](), [ubuntu](), [ubuntu-linux]() ### AI overview This tutorial explains how to identify Debian and Ubuntu packages in the "rc" state, meaning the package was removed but its configuration files remain. It shows how to list these packages and purge their leftover configuration files with apt, dpkg, grep, and awk commands. ### Source excerpt In Debian and Ubuntu Linux, an "rc" status package means the package has been uninstalled, but its configuration files remain on the disk and take up space. Sometimes, certain directories are also in the /var/ directory. When you type the sudo apt remove pkg1 command, it deletes most of the data, but config files are left alone in case you reinstall that package again. You can free up disk space by removing unwanted config files. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to uninstall packages marked "rc" on Debian / Ubuntu Linux appeared first on nixCraft. ## How to use find command to delete all \*.log files created in last 90 days except for last 7 days DevFeed: [How to use find command to delete all \*.log files created in last 90 days except for last 7 days]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-05-15T06:56:03Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Linux](), [Containers](), [Unix](), [macOS](), [freebsd]() Tags: [commands](), [containers](), [disk-space](), [easy](), [freebsd](), [how-to](), [linux](), [macos](), [unix]() ### AI overview A practical guide to using find to identify and permanently delete .log files older than 7 days but newer than 90 days. It recommends listing and verifying the results before deletion and notes compatibility with Linux, FreeBSD, and macOS. ### Source excerpt I have log files created whenever I patch or rebuild Linux containers. They are taking disk space. The logs are helpful if something fails. Otherwise, after a few weeks, those log files have no usage for me. So here is a quick tip on how to use the find command to delete all *.log files created in the last 90 days except for the previous 7 or 10 days. The commands mentioned in these tips are compatible with the Linux, FreeBSD, and macOS versions of the find command. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to use find command to delete all *.log files created in last 90 days except for last 7 days appeared first on nixCraft. ## What's new in pgvector v0.7.0 DevFeed: [What's new in pgvector v0.7.0]() Original publisher: [Read original article]() Author: Pavel Borisov Published: 2024-05-02T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [datasets](), [build times](), [IO](), [Arm]() Tags: [architecture](), [arm](), [build-times](), [comparison](), [datasets](), [disk-space](), [embedding](), [features](), [memory](), [net](), [performance](), [postgres](), [speed](), [vector]() ### AI overview The article describes pgvector v0.7.0 features for reducing vector storage and memory use, including float16, sparse, and bit vector representations. It focuses on float16 HNSW indexes, which use half the memory and can improve parallel build performance, while also discussing disk-space savings and ARM-specific behavior. ### Source excerpt Exploring new features in pgvector v0.7.0 ## Filtering Process Output With tee DevFeed: [Filtering Process Output With tee]() Original publisher: [Read original article]() Published: 2024-02-10T10:11:00Z Content type: tutorial Language: en Sources: [Gunnar Morling]() Topics: [Java](), [Kubernetes](), [Logging](), [Streams]() Tags: [capture](), [disk-space](), [files](), [filter](), [java](), [jvm](), [kubernetes](), [logging](), [redirection]() ### AI overview This tutorial explains how to use tee and process substitution to expose complete Java process output to Kubernetes logging while writing only filtered lines to a log file. It also discusses preventing unbounded log growth and illustrates how process substitution uses file descriptors and pipes. ### Source excerpt Recently I ran into a situation where it was necessary to capture the output of a Java process on the stdout stream, and at the same time a filtered subset of the output in a log file. The former, so that the output gets picked up by the Kubernetes logging infrastructure. The letter for further processing on our end: we were looking to detect when the JVM stops due to an OutOfMemoryError, passing on that information to some error classifier. ## Can Debezium Lose Events? DevFeed: [Can Debezium Lose Events?]() Original publisher: [Read original article]() Published: 2023-11-14T14:00:00Z Content type: article Language: en Sources: [Gunnar Morling]() Topics: [data observability](), [Replication](), [Database](), [configuration](), [MySQL](), [Amazon RDS]() Tags: [amazon-rds](), [configuration](), [data-engineering](), [database](), [disk-space](), [mysql](), [replication](), [sql-server]() ### AI overview The article explains that Debezium should generally not miss database change events because its delivery semantics are at-least-once. Event loss can occur when operational issues cause required transaction-log data to be discarded before a connector captures it, such as when retention limits are exceeded during extended downtime. It discusses retention behavior for MySQL, Amazon RDS, SQL Server, and PostgreSQL replication slots. ### Source excerpt This question came up on the Data Engineering sub-reddit the other day: Can Debezium lose any events? I.e. can there be a situation where a record in a database get inserted, updated, or deleted, but Debezium fails to capture that event from the transaction log and propagate it to downstream consumers? ## Transfer many large files from Android DevFeed: [Transfer many large files from Android]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2022-12-17T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Android](), [adb](), [Command-line interface](), [Shell]() Tags: [adb](), [android](), [backup](), [blogs](), [disk-space](), [dry-run](), [files](), [large-files](), [storage]() ### AI overview A tutorial on using ADB to transfer many large files from an Android phone when Android File Transfer is unreliable or disk space is limited. It explains pulling files in batches and safely deleting only files that were synchronized. ### Source excerpt Trying to get a large number of files from your Android phone, but Android File Transfer freezing up? Here's what I learned trying to pull ~170 Gb from my Pixel phone. ## Investigating WAL Growth from an Inactive Postgres Replication Slot on Amazon RDS DevFeed: [Investigating WAL Growth from an Inactive Postgres Replication Slot on Amazon RDS]() Original publisher: [Read original article]() Published: 2022-11-30T13:00:00Z Content type: article Language: en Sources: [Gunnar Morling]() Topics: [Replication](), [Amazon RDS](), [apache-flink](), [Database]() Tags: [amazon](), [amazon-rds](), [apache-flink](), [database](), [debezium](), [disk-space](), [postgres](), [replication](), [storage]() ### AI overview This article investigates how an inactive Postgres replication slot on Amazon RDS can retain WAL segments and consume disk space even when the database appears idle. It reproduces the behavior and compares replication-slot LSN differences with RDS storage and transaction-log metrics. ### Source excerpt Table of Contents The Observation The Solution Take Away While working on a demo for processing change events from Postgres with Apache Flink, I noticed an interesting phenomenon: A Postgres database which I had set up for that demo on Amazon RDS, ran out of disk space. The machine had a disk size of 200 GiB which was fully used up in the course of less than two weeks. Now a common cause for this kind of issue are replication slots which are not advanced: in that case, Postgres will hold on to all WAL segments after the latest log sequence number (LSN) which was confirmed for that slot. Indeed I had set up a replication slot (via the Decodable CDC source connector for Postgres, which is based on Debezium). I then had stopped that connector, causing the slot to become inactive. The problem was though that I was really sure that there was no traffic in that database whatsoever! What could cause a WAL growth of ~18 GB/day then? ## Managing Disk Space With "ncdu" DevFeed: [Managing Disk Space With "ncdu"]() Original publisher: [Read original article]() Author: James Brooks Published: 2022-01-06T10:50:00Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Linux](), [Provisioning](), [Server](), [Terminal](), [Script]() Tags: [disk-space](), [errors](), [free](), [linux](), [provisioning](), [server](), [terminal]() ### AI overview This article explains how to manage disk space on Linux servers using du and ncdu. It describes using ncdu's navigable ncurses interface to locate large files and directories, remove unnecessary files, and investigate Forge-related files when disk-usage errors persist. ### Source excerpt Linux ships with a useful command called `du` (Disk Usage), which is used to find the size of files and directories. When provisioning your server, Forge installs `ncdu` which is an advanced version of `du` that allows you to easily navigate your directories via an ncurses interface. This makes it much quicker to identify large files and directories. ## Homebrew - uninstall formula with dependencies DevFeed: [Homebrew - uninstall formula with dependencies]() Original publisher: [Read original article]() Author: Tom Published: 2021-11-05T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Homebrew](), [macOS]() Tags: [bash](), [brew-autoremove](), [clean-uninstall-homebrew](), [command](), [dependencies](), [disk-space](), [homebrew](), [homebrew-uninstall-dependencies](), [how-to](), [macos](), [macos-brew-tips](), [macos-package-management](), [packages](), [remove-homebrew-formula]() ### AI overview A tutorial on uninstalling a Homebrew formula and its dependencies on macOS. It recommends using brew autoremove, while warning that the command may remove packages you still need, so users should review its output carefully. ### Source excerpt Learn how to uninstall a Homebrew formula along with its dependencies on MacOS, ensuring a clean removal and freeing up disk space. ## Searching for RH Counterexamples -- Scaling Up DevFeed: [Searching for RH Counterexamples -- Scaling Up]() Original publisher: [Read original article]() Published: 2021-02-16T09:00:00Z Content type: article Language: en Sources: [Jeremy Kun]() Topics: [Mathematics](), [hashing](), [scaling](), [sha256](), [hash](), [Database]() Tags: [architecture](), [disk-space](), [hashing](), [mathematics](), [performance](), [postgres](), [programming](), [refactor](), [riemann-hypothesis](), [scaling](), [sha256](), [software]() ### AI overview This article describes scaling a search for counterexamples to the Riemann Hypothesis. It focuses on reducing storage by keeping deterministic SHA-256 summaries instead of every witness value and refactoring the application into a worker architecture. ### Source excerpt We're ironically searching for counterexamples to the Riemann Hypothesis. Setting up Pytest Adding a Database Search Strategies Unbounded integers Deploying with Docker Performance Profiling Last time we made the audacious choice to remove primary keys from the RiemannDivisorSums table for performance reasons. To help with that, we will do two things in this post Reduce the storage footprint of the whole application (it was 60 GiB when it crashed, and we got up to 84 prime factors). ## How We Solved a Storage Problem in PostgreSQL Without Adding a Single Byte of Storage DevFeed: [How We Solved a Storage Problem in PostgreSQL Without Adding a Single Byte of Storage]() Original publisher: [Read original article]() Author: Haki Benita Published: 2018-12-21T22:00:00Z Content type: tutorial Language: en Sources: [Haki Benita]() Topics: [PostgreSQL](), [etl](), [Database](), [hash](), [Sorting]() Tags: [articles](), [dataset](), [disk-space](), [dump](), [etl](), [hash](), [performance](), [postgresql](), [query](), [sorting](), [sql](), [storage]() ### AI overview This article explains how an ETL task for removing duplicate binary records in PostgreSQL caused increasing temporary disk-space usage. The author reduced the sorting key by hashing the binary value with md5, lowering additional disk usage from about 30 MB to about 4 MB without adding storage. ### Source excerpt A while back we started getting alerts in the middle of the night on low disk space. A quick investigation led us to one of our ETL tasks. Every night the task was fired to eliminate duplicate dumps, and free up some space. This is a short story about how we found our silver bullet and solved the issue without adding a single byte of storage. ## Docker Commands and Tips for Managing Containers and Images DevFeed: [Docker Commands and Tips for Managing Containers and Images]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2015-05-10T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Docker](), [container](), [docker images]() Tags: [commands](), [container](), [containers](), [disk-space](), [docker](), [docker-images](), [mac]() ### AI overview A collection of Docker commands and practical tips for managing containers and images, including stopping containers, removing stopped containers, deleting images, and using Kitematic on Mac. ### Source excerpt Like my old post on git, this is somewhat a collection of useful Docker commands/tricks/whatever.