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
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes