On Tuesday, October 27, 2009 11:41am, "Thomas Hervé" <[email protected]> said: > Le mardi 27 octobre 2009 à 11:09 -0400, Dan Halbert a écrit :
>> Should I be doing something else, or is this a slightly different case of the >> problem? > > AFAICT, it's not the same problem. You don't observer a leak, just a > performance hit due to the system used by mutable variables. As long as > your object is in the cache, the variable will be there as well. > store.invalidate should clean it (called by commit and rollback). > Thanks for the diagnosis. That is what I first thought but wasn't so sure when I read the email string. I added an invalidate() and fixed the problem for now. block_implicit_flushes() also worked, but the invalidate() is cleaner. >> My thought after studying this (but before seeing the emails) is that I might >> like Storm to provide Tuple and TupleVariable classes in addition to List and >> ListVariable. Since the Tuple would be immutable, it would not have to be >> checked >> for changes when a flush() occurs. > > That may be interesting indeed. Dealing with arrays of things is a large part of my code, so I may try to work on Tuples if I keep running into this performance issue. Dan -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
