Larger payloads (32MB) for telemetry

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
7 days ago

People

(Reporter: kparlante, Assigned: trink)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Comment hidden (empty)

Comment 1

4 years ago
The build script in the repo over in bug 1122754 sets the payload size to 8MB (increased from 64KB) -- we can change it there as needed.

See:
https://github.com/mreid-moz/data-pipeline/blob/master/bin/build_pipeline_heka.sh#L20
Status: NEW → RESOLVED
Last Resolved: 4 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
(Assignee)

Comment 2

4 years ago
fyi: in Heka's default configuration this could consume over 3.2GiB of memory.  If we set it any larger we should reduce the message pool size.

Comment 3

4 years ago
What are the implications of reducing the pool size?
(Assignee)

Comment 4

4 years ago
It all depends on the configuration and data profile but the worst cases:
1) reduced throughput
2) reduced number of messages that the decoder can output in a 1 to N case (hangs if exceeded)

Updated

7 days ago
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.