Mikhail Shilkov • 5/25/2021

Choosing the Number of Shards in Temporal History Service

Read Original

This technical article details the critical configuration of shard count in Temporal's History service. It explains how too few shards cause lock contention and latency, while too many waste resources, using experimental data from the Maru benchmarking tool to illustrate performance impacts.

0 comments
#performance tuning #Sharding #Load Testing
Choosing the Number of Shards in Temporal History Service

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes