db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dag.wan...@oracle.com (Dag H. Wanvik)
Subject Re: (DERBY-4908) Instability in CheckConstraintTest.testBuiltInFunctions
Date Sat, 20 Nov 2010 00:21:07 GMT
Knut Anders Hatlen <knut.hatlen@oracle.com> writes:

> I think the memory footprint and the available memory are also used to
> determine the cost of a hash scan (if it doesn't fit in main memory, it
> will be considered more expensive).

That seems a good condicate culprit here, especially when running the
entire test suite. I guess people run with different heap sizes.. and/or
we have some leakage. Not sure if anyone has tested to leaks recently?



View raw message