---
title: "Discussion on \"TimescaleDB Memory Tuning: shared_buffers, work_mem, and Chunk Sizing\" | Hashnode"
description: "Discussion on \"TimescaleDB Memory Tuning: shared_buffers, work_mem, and Chunk Sizing\". TimescaleDB Memory Tuning: shared_buffers, work_mem, and Chunk Sizing\nI frequently encounter TimescaleDB deployments where the team has followed standard PostgreSQL tuning advice -- 25% shared_buffers, bump work_mem a bit, set effective_cache_size --..."
url: "https://hashnode.com/posts/timescaledb-memory-tuning-sharedbuffers-workmem-and-chunk-sizing/69afeba3fbcdb0cc1aebe31f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [TimescaleDB Memory Tuning: shared\_buffers, work\_mem, and Chunk Sizing](https://postgresdba.hashnode.dev/timescaledb-memory-tuning-sharedbuffers-workmem-and-chunk-sizing?utm_source=hashnode&utm_medium=feed)

TimescaleDB Memory Tuning: shared\_buffers, work\_mem, and Chunk Sizing I frequently encounter TimescaleDB deployments where the team has followed standard PostgreSQL tuning advice -- 25% shared\_buffers, bump work\_mem a bit, set effective\_cache\_size --...

Mar 10 · 5 min read · postgresdba.hashnode.dev  
Read the article

-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#timescaledb](https://hashnode.com/tag/timescaledb)
-   [#tuning](https://hashnode.com/tag/tuning)
-   [#performance](https://hashnode.com/tag/performance)
-   [#database](https://hashnode.com/tag/database)

## Written by

[Philip McClarence](https://hashnode.com/@pgdba)

@pgdba · London, UK

  
[View profile](https://hashnode.com/@pgdba)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
