You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to disable the formation of a reverse index? Now, when because of it due to the growth of the table, queries are use a lot of memory. Moreover, in the old Tree schema, where I do not use a reverse index, there is no such problem.
Comparing Type Index vs Tree,
For Tree
enough 10Gb for Index need 50Gb (Error: Storage read limit for memory )
The text was updated successfully, but these errors were encountered:
Not at this time. Disabling reverse index is performance problem for some queries, for example
a.*.b.c.d
or {a,ab}.*.b.c.d
On large system it's wery heavy. queries are use a lot of memory - what queries ? For some queries graphite-clickhouse can be tuned for use direct/reverse index.
If you past query examples, auto detect can be improved also (may be need a open issue in graphite-clickhouse).
Is it possible to disable the formation of a reverse index? Now, when because of it due to the growth of the table, queries are use a lot of memory. Moreover, in the old Tree schema, where I do not use a reverse index, there is no such problem.
Comparing Type Index vs Tree,
For Tree
enough 10Gb for Index need 50Gb (Error: Storage read limit for memory )
The text was updated successfully, but these errors were encountered: