-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Excessive memory usage #34
Comments
Okay, I managed to setup a memory profiling session using dotTrace's memory profiler. The TrackStream seems to have moved into the OptimisticPipelineHook, which is the culprit of all this. Next to a maximum for the number of commits tracked per stream, maybe there should be a maximum number of streams tracked. There should be a choice of tracking or not tracking in the WireUp extensions,in essence more control over the pipeline using e.g. an IPipelineHookBuilder. This way there would be choice between the built-in builder or a custom builder. There's a good example of this pipeline building in WSE3 (yeah, I know, don't ask). |
Could you resubmit this as a new issue? For some reason it got closed like you said... Also, I'm looking at potentially using a bloom filter to keep memory usage down. |
Sure, I'll do that. Regards, Verstuurd vanaf mijn iPhone Op 8-apr.-2011 om 05:14 heeft joliverreply@reply.github.com het volgende geschreven:
|
I know that's a little vague but if you insert lots (>100000) of events in a loop using sql persistence, I notice lots of memory is used and not freed up. I'm not sure it's an actual issue, just weird that it keeps growing. At first I thought it was the tracker, but that seems gone from the source. I must be doing something wrong ...
I observed this behavior using a compiled version of 403e4ce
Code I used during which the behavior was observed (.NET 4.0):
The text was updated successfully, but these errors were encountered: