Check, test and tune pool-of-connections and max_connections configuration
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	jcrespo
	Sep 13 2015, 5:52 PM

Description

Current configuration may be too conservative regarding realibility, and we may be able to get more QPS by having more concurrency and less queing.

Event Timeline

jcrespo created this task.Sep 13 2015, 5:52 PM

jcrespo claimed this task.

jcrespo raised the priority of this task from to High.

jcrespo updated the task description. (Show Details)

jcrespo added projects: DBA, acl*sre-team.

jcrespo subscribed.

Restricted Application added subscribers: Matanya, Aklapper. · View Herald TranscriptSep 13 2015, 5:52 PM

jcrespo moved this task from Triage to Backlog on the DBA board.Sep 15 2015, 11:01 AM

jcrespo moved this task from Backlog to In progress on the DBA board.Oct 19 2015, 6:17 PM

I've set all nodes to 32 in configuration. According to all benchmarks, 32-36 are the maximum practical limit for concurrent threads. We could use proper benchmarking for better tuning, but it should be good enough for now to solve the most immediate problems.

I will have a look at max_connections now.

This requires long-term monitoring, but I have found no issues so far. Closing as resolved for now, will reopen if issues are actually found.

Check, test and tune pool-of-connections and max_connections configurationClosed, ResolvedPublicActions

Description

Event Timeline

Check, test and tune pool-of-connections and max_connections configuration
Closed, ResolvedPublic
Actions