It is impossible to estimate what is more critical because it would require prototypes for every idea to estimate the impact. Instead, we should start working on the simplest things, such as IGINTE-8386 [1] or IGNITE-8384 [2]. And then gradually swtich to more and more complex changes.
[1] https://issues.apache.org/jira/browse/IGNITE-8386 [2] https://issues.apache.org/jira/browse/IGNITE-8384 On Wed, Apr 25, 2018 at 10:02 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Thanks, Vladimir! > > Looking at this IEP, it is not clear which tickets are more critical than > others. Also, the complexity of each ticket is unknown. Is there a way to > provide this information? > > D. > > On Wed, Apr 25, 2018 at 10:21 PM, Vladimir Ozerov <voze...@gridgain.com> > wrote: > > > Igniters, > > > > I heard a lot of complains around performance of our SQL indexes. > Notably - > > slow updates and slow execution of CREATE INDEX command on large data > sets. > > I summarized all known possible optimizations under a single IEP [1]. We > > need to start working in this direction, starting from the most simple > and > > obvious things. > > > > Please feel free to review IEP tickets and share additional suggestions > or > > comments or what else could be done to make our indexes faster. > > > > Vladimir. > > > > [1] > > https://cwiki.apache.org/confluence/display/IGNITE/IEP- > > 19%3A+SQL+index+update+optimizations > > >
