Score:2

CouchDB replication tanks performance

tr flag

We have an API implemented in Tornado using CouchDB as it's backend.

Usually, queries to CouchDB finishes in less than 50ms.

But lately, queries takes up to 250ms, sometimes more. After some New Year's Day troubleshooting, we figured out that replication tanks performance so much, we disabled it, and performance rose again.

Last night around midnight (UTC+7) we reenabled replication, no impact. But this morning when the API starts to see high loads, the CouchDB performance tanked again.

  1. Is there a way to troubleshoot this performance issue?
  2. If replication turns out to be the culprit, how to optimize replication?
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.