Execution Time is too long

[kldcxy-1]

I see presto web ui, and i see that Execution Time is too long, so how make it better?

[rohanpednekar]

Can you share more information including -

Presto Version
Table DDLs
Quarries
Query Explain plans
Current configs, JVM Flags?
Source of your data, any additional connectors
Infrastructure configs
and any additional optimization you have already tried?

[kldcxy-1]

Presto Version 0.265
Quarries show tables from MySQL.jimu_report
Query Explain plans

Current configs, JVM Flags

coordinator=true
node-scheduler.include-coordinator=true
http-server.http.port=8080
query.max-memory=50GB
query.max-memory-per-node=1GB
query.max-total-memory-per-node=2GB
discovery-server.enabled=true
discovery.uri=http://localhost:8080

-server
-Xmx16G
-XX:+UseG1GC
-XX:G1HeapRegionSize=32M
-XX:+UseGCOverheadLimit
-XX:+ExplicitGCInvokesConcurrent
-XX:+HeapDumpOnOutOfMemoryError
-XX:+ExitOnOutOfMemoryError

Above is the deployment configuration for my use

Now presto has been running for a few days and now performance is improving is presto performance related to the length of deployment

[kldcxy-1]

Can you share more information including -

Presto Version Table DDLs Quarries Query Explain plans Current configs, JVM Flags? Source of your data, any additional connectors Infrastructure configs and any additional optimization you have already tried?

Presto Version 0.265
Quarries show tables from MySQL.jimu_report
Query Explain plans
image

Current configs, JVM Flags

coordinator=true
node-scheduler.include-coordinator=true
http-server.http.port=8080
query.max-memory=50GB
query.max-memory-per-node=1GB
query.max-total-memory-per-node=2GB
discovery-server.enabled=true
discovery.uri=http://localhost:8080

-server
-Xmx16G
-XX:+UseG1GC
-XX:G1HeapRegionSize=32M
-XX:+UseGCOverheadLimit
-XX:+ExplicitGCInvokesConcurrent
-XX:+HeapDumpOnOutOfMemoryError
-XX:+ExitOnOutOfMemoryError

Above is the deployment configuration for my use

Now presto has been running for a few days and now performance is improving is presto performance related to the length of deployment

[kldcxy-1]

Can you share more information including -

Presto Version Table DDLs Quarries Query Explain plans Current configs, JVM Flags? Source of your data, any additional connectors Infrastructure configs and any additional optimization you have already tried?