I see a few OOM errors in the logs for rendering.mobile. Are there any metrics or histograms or sample diagnostics that can be disabled to shrink the result set?

+chiniforooshan@

We have removed the TBMv1 metrics, and now report only the TBMv2 metrics. I don't believe there are any redundant metrics we can remove at the moment.

Is there any more details about the OOMs (e.g. what tools, what it is trying to do etc.)? If we were able to reduce the size of pageset, would that help?

"Exceeded soft memory limit of 2048 MB with 2462 MB after servicing 190 requests total".

I'm not sure whether that means that reducing the number of stories by 20% would fix it, but I doubt it.

There's a temporary hack in the dashboard to remove all sample diagnostics. You could do that before uploading, but it still might not help, and it would make it harder to remove the hack later.

One relatively easy fix that would definitely fix the OOMs would be to upload results for one story at a time, plus another upload for the summary timeseries.
I'd be happy to add a flag to add_reserved_diagnostics to write multiple files if you can change the recipes to upload multiple files separately. WDYT?

See more recent thinking about batching histograms in https://bugs.chromium.org/p/chromium/issues/detail?id=921236

This seems to be working fine, is there anything to do here?

Looks like there is new data there now, so I guess it got fixed on its own.