...
P202 (events/s) | P300 (events/s) | P202\:P300 ratio |
|---|---|---|
6.71 | 2.45 | 2.74 |
RECON File size
P202 (kB/event) | P300 (kB/event) | P300\:P202 |
|---|---|---|
14.67 | 37.27 | 2.54 |
Also see spreadsheet for exact numerology.
...
- P202 max mem after processing ~96,000 events
- P300 max mem after processing only ~20,000 events
- P300 starts at ~600MB and has a mem leak of ~55kB/event, which limits clump size. At ~60k-80k events, memory consumption has grown to make crashes inevitable, e.g.,
The exact time of a crash is unpredictable as it depends on the total memory resources and usage on a particular machine.Code Block terminate called after throwing an instance of 'std::bad_alloc' what(): St9bad_alloc sh: line 1: 25973 Aborted Gleam