Hello n8n community,
I’ve recently started developing with n8n on a self-hosted setup and have been very impressed. However, I’ve encountered infrastructure issues related to the database’s disk space.
The feature that saves execution data for logging and auditing is incredibly useful. The downside is that it causes rapid growth in database size. I know we can configure data pruning or disable saving executions entirely, but these options don’t fully meet our needs, as I often need to review past executions.
I would like to propose a solution: save all execution data to the database in a compressed format (like Gzip). When a user wants to view a past execution in the editor, the compressed data would be sent to the client, and the browser would handle the decompression.
This would lead to a substantial reduction in disk space requirements for the n8n database. Although there would be a slight increase in CPU usage on the server for compression, this trade-off is more than acceptable compared to the high costs of scaling database storage. The decompression task, being handled client-side, would efficiently distribute the workload.
Thank you for considering this suggestion.