Keep scan memory consumption constant
Reported by Ben Hood | July 21st, 2011 @ 06:36 AM | in 0.9-series (closed)
During scans, unmatched events are not emitted until after the scan completes. In some cases this could consume a lot of memory. Hence we should look into ways that this can be bounded or overflowed to disk. This may get solved as part of #294.
Comments and changes to this ticket
-

Ben Hood August 30th, 2011 @ 07:34 AM
- Tag set to persistent session events
-

Ben Hood August 30th, 2011 @ 07:36 AM
- State changed from new to invalid
Invalidating this ticket as the persistent diffs (#294 et al) should take of this issue.
-

Ben Hood November 14th, 2011 @ 05:35 PM
- Milestone set to 0.9-series
- Milestone order changed from 88 to 0
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.