You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Denys Ordynskiy (JIRA)" <ji...@apache.org> on 2019/07/08 17:00:00 UTC

[jira] [Closed] (DRILL-6814) Query performance on S3 files

     [ https://issues.apache.org/jira/browse/DRILL-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denys Ordynskiy closed DRILL-6814.
----------------------------------
    Resolution: Cannot Reproduce

> 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)