New Splitting strategy: running into assertion failure in newSplitting method

[Christian Humer]

Hi Stefan,

The assumption does in fact not hold yet. This needs a fix. Will remove it
for now.

Regarding the warmup time -G:-TruffleSplittingClassInstanceStamps should
bring it again to a reasonable level. I think I will push this as a default
because I've seen class instance stamps to have no visible influence on
peak performance but horrible influence on startup time. Can you confim
that?

Thanks.


- Christian Humer


On Thu, Jul 24, 2014 at 10:48 PM, Stefan Marr <java at stefan-marr.de> wrote:

> Hi Christian:
>
> I updated to the latest version of Graal and tried the new splitting
> heuristic.
> Overall it seems to be a win for TruffleSOM. Warmup up time seems to
> increase significantly, and two benchmarks suffer, but overall results seem
> to be positive.
>
> However, on all benchmarks I tested manually, I was running into an
> assertion error.
> (at
> com.oracle.graal.truffle.DefaultTruffleSplittingStrategyNew.newSplitting(DefaultTruffleSplittingStrategyNew.java:102))
>
> It doesn’t seem to cause any visible issues, but the assumption of the
> assertion does not hold.
>
> Best regards
> Stefan
>
>
> --
> Stefan Marr
> INRIA Lille - Nord Europe
> http://stefan-marr.de/research/
>
>
>
>