Enable ingestion alerts for Flame (319MB)

RESOLVED FIXED

Status

Datazilla
General
P1
normal
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: davehunt, Assigned: davehunt)

Tracking

({perf})

Details

(Whiteboard: [c=automation p= s= u=])

Attachments

(1 attachment)

(Assignee)

Description

4 years ago
+++ This bug was initially created as a clone of Bug #1024924 +++

We're now running performance tests on Flame with memory restricted to 379MB. This is now our primary target, so we should enable the ingestion alerts.
(Assignee)

Comment 1

4 years ago
Created attachment 8466130 [details] [diff] [review]
Enable ingestion alerts for Flame (319MB). v1.0
Assignee: nobody → dave.hunt
Status: NEW → ASSIGNED
Attachment #8466130 - Flags: review?(jeads)

Updated

4 years ago
Keywords: perf
Priority: -- → P1
Summary: Enable ingestion alerts for Flame (379MB) → Enable ingestion alerts for Flame (319MB)
Whiteboard: [c=automation p= s= u=]
(Assignee)

Updated

4 years ago
Attachment #8466130 - Attachment description: Enable ingestion alerts for Flame (379MB). v1.0 → Enable ingestion alerts for Flame (319MB). v1.0
I'm planning on landing this with the fixes to Bug 1046056
Comment on attachment 8466130 [details] [diff] [review]
Enable ingestion alerts for Flame (319MB). v1.0

Review of attachment 8466130 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good.
Attachment #8466130 - Flags: review?(jeads) → review+
Depends on: 1054452
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.