[
https://issues.apache.org/jira/browse/DRILL-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735855#comment-16735855
]
Denys Ordynskiy edited comment on DRILL-6814 at 1/7/19 2:05 PM:
----------------------------------------------------------------
Tests from the drill-test-framework for Drill fragments were passed. Drill
successfully created major and minor fragments for a S3 storage.
was (Author: denysord88):
Tests from the drill-test-framework for Drill fragments were passed. Drill
successfully creating major and minor fragments for a S3 storage.
> 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: Denys Ordynskiy
> Priority: Major
> Attachments: S3investigate.txt
>
>
> 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)
