Community
Participate
Working Groups
In many cases, it would probably make more sense to experiment with eliminating result caching in with check / eval Rete nodes, as opposed to implementing even more caching. There could be a separate indicator (annotation or hint) to apply on exceptional evaluations that are very costly (e.g. difficult string operations?) and should be cached.
New Gerrit change created: https://git.eclipse.org/r/83711
Gerrit change https://git.eclipse.org/r/83711 was merged to [master]. Commit: http://git.eclipse.org/c/viatra/org.eclipse.viatra.git/commit/?id=6758ec49e7a96df198a843b4ef83b2ab7e8de594
Evaluator nodes are now non-caching by default. This might save some memory. A Rete hint has been introduced to override this default at planning time. Future work: expression-specific intelligence? Future work: query planning for better caching (in case caching is needed).
As this has caused performance regressions, please change the default behavior back as it was before.
New Gerrit change created: https://git.eclipse.org/r/91919
Gerrit change https://git.eclipse.org/r/91919 was merged to [master]. Commit: http://git.eclipse.org/c/viatra/org.eclipse.viatra.git/commit/?id=08107e47fb52a5ce78f4e6dcf4dd34e3bdc72739
New Gerrit change created: https://git.eclipse.org/r/92340
New Gerrit change created: https://git.eclipse.org/r/92351
Gerrit change https://git.eclipse.org/r/92351 was merged to [1.5-maintenance]. Commit: http://git.eclipse.org/c/viatra/org.eclipse.viatra.git/commit/?id=e52e19cc29084ed7716945a54278b4ff1c857e75
Is anything remaining for this ticket or can it be closed?