you can add
-XX:+PrintGCDateStamps
-XX:+PrintGCApplicationStoppedTime
-XX:+PrintGCDetails
-Xloggc:/var/presto/data/var/log/presto-gc.log
into you jvm.properties, if you think there is a gc issue , you can check
the GC logs.
--
View this message in context:
http://apache-carbondata-dev-mailing
there is no obvious issue in your configuration, did you have finish testing
on ORC?
--
View this message in context:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/DISCUSSION-CarbonData-Integration-with-Presto-tp16793p18338.html
Sent from the Apache CarbonData Dev M
hi, did you test orc vs carbondata with configuration as I suggested?
--
View this message in context:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/DISCUSSION-CarbonData-Integration-with-Presto-tp16793p17419.html
Sent from the Apache CarbonData Dev Mailing List archi
for your first testing, What configuration tuning did you make for
carbondata? and could you provide a detailed testing report including
create table sqls, the row numbers of tables etc.
--
View this message in context:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/DI
Hi
1 you can set -XX:ReservedCodeCacheSize in JVM.propertes, make it big
2 I don't see your discovery.uri IP, make user Master act as coordinate and
discovery server;
3 remove query.max-memory-per-node firstly.
4 you can test orc, parquet is not support very well on presto.
thanks
--
View thi
Can you give me your all configuration files (etc/) of coordinate and worker,
What configuration tuning did you make for carbondata?
A lot of scenes in our company are using Presto,I have tested presto read
orc vs carbondata , Carbondata is clearly inferior to Orc;
During the testing, for perfor
