I noticed that between runs my cache hit rate using dogpile query caching
could change without any of the underlying data structures changing, after
digging in what I found was the join order on my polymorphic classes is not
deterministic. Is there any way to ensure a deterministic join order
when you say between runs, you mean whole new processes with new mappers,
right? there are some memoized sets involved in polymorphic loading, those
sets should not change order as the program runs but across runs there may be
some changes in order.to improve this I'd need you to provide a
Michael,
That works!
Amir
On Thursday, July 11, 2013 11:17:27 AM UTC-7, Michael Bayer wrote:
when you say between runs, you mean whole new processes with new
mappers, right? there are some memoized sets involved in polymorphic
loading, those sets should not change order as the program
just that, huh. the tricky thing is its difficult to ensure that a set()
doesn't find its way in there at some point and mess the order up again.
open up a ticket for this one I'd need to come up with a test.
On Jul 11, 2013, at 2:19 PM, Amir Elaguizy aelag...@gmail.com wrote:
http://www.sqlalchemy.org/trac/ticket/2779
On Thursday, July 11, 2013 11:23:32 AM UTC-7, Michael Bayer wrote:
just that, huh. the tricky thing is its difficult to ensure that a set()
doesn't find its way in there at some point and mess the order up again.
open up a ticket for this one
