- 100 platform events published for Foo__e in the same second
- Each platform event represents 100K of data (10MB data altogether across the 100 events)
- SFDC presents the events to the subscribing trigger Foo.trigger
- Does the SFDC event "batcher" consider whether the heap size of Foo.trigger would be breached when deciding on the batch size?
In my example, would the SFDC event batcher present only < 60 events (< 6MB) as that is less than the 6MB Heap avail?
Rationale for question: I have a 3rd party system that is publishing events, each with payloads of 256K. If the upstream publisher publishes many events all at once, the trigger's heap could be breached.
I know that summer 19 gives me more control over the size of the Trigger batch for processing (CPU/heap limit management) but not sure this will solve the trigger blowing up in the first place before it ever gets out of the starting block.