From 3f6a7483e64c907e4af2e87427321e65e77b169c Mon Sep 17 00:00:00 2001 From: Bryan Newbold Date: Wed, 21 Nov 2018 22:21:52 -0800 Subject: update notes/TODO --- notes/performance/kafka_pipeline.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'notes/performance/kafka_pipeline.txt') diff --git a/notes/performance/kafka_pipeline.txt b/notes/performance/kafka_pipeline.txt index 0a503a18..0ff2e411 100644 --- a/notes/performance/kafka_pipeline.txt +++ b/notes/performance/kafka_pipeline.txt @@ -29,3 +29,19 @@ elastic-release python processing is at 66% (of one core) CPU! and elastic at ~30%. Huh. But, in general, "seems to be working". + +## End-To-End + +release-updates: 40/sec +api-crossref: 40/sec +api-datacite: 15/sec +changelog: 11/sec +consumer_offsets: 0.5/sec + +elastic indexing looks like only 8/sec or so. Probably need to batch. + +Tried running additional fatcat-elasticsearch-release-worker processes, and +throughput goes linearly. + +Are consumer group names not actually topic-dependent? Hrm, might need to +rename them all for prod/qa split. -- cgit v1.2.3