[
https://issues.apache.org/jira/browse/DRILL-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669518#comment-16669518
]
Ashish Shukla edited comment on DRILL-6814 at 10/31/18 2:46 AM:
----------------------------------------------------------------
[~kkhatua] I had to terminate the EC2 instances and don't have the stats right
now.But one thing I observed while going though the profile that it had created
too many batches(approx . 9000) and approx 10k record in every batch while
reading in case of S3 files.
was (Author: ashishkshukladb):
[~kkhatua] I had to terminate the EC2 instances and don't have the stats right
now
> Query performance on S3 files
> -----------------------------
>
> Key: DRILL-6814
> URL: https://issues.apache.org/jira/browse/DRILL-6814
> Project: Apache Drill
> Issue Type: Improvement
> Components: Storage - Other
> Affects Versions: 1.14.0
> Environment: Amazon EC2 instances-
> 4 Linux Redhat machines -version 7.5
> RAM- 32GB
> Reporter: Ashish Shukla
> Assignee: Robert Hou
> Priority: Major
>
> I have installed 4 Node drill cluster on Amazon EC2 and trying to execute a
> simple count on one Amazon S3 file. File type is CSV and size is approx- 14GB.
> The query returns expected count after the execution of approx 30 minutes.
> If we keep the same file in hdfs or create a table in postgres, execution
> time is relatively very less (approx 2-3 minutes).
> Is it normal behavior or something can be done for S3 files to make
> execution time comparable ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
