ygerzhedovich commented on code in PR #2960:
URL: https://github.com/apache/ignite-3/pull/2960#discussion_r1434014617
##########
modules/sql-engine/src/main/java/org/apache/ignite/internal/sql/engine/prepare/IgnitePlanner.java:
##########
@@ -133,6 +133,12 @@ public class IgnitePlanner implements Planner,
RelOptTable.ViewExpander {
private RelOptCluster cluster;
+ static {
+ // Preload some classes to reduce first planning time.
Review Comment:
In the fact visible time of first planning will be the same.
I see tow options here:
1) Move loading and initialization classes on earlier stage, during node
startup. Due to java could do classpoading in parallel it shouldn't significant
increase time of node start, but our very first parsing will be visible faster.
For tests which could instantiate some of services himself we could keep
initialization in two places.
2) Just fix a coomet to show real life )
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
