You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Carl Boettiger (Jira)" <ji...@apache.org> on 2022/09/01 20:54:00 UTC

[jira] [Created] (ARROW-17597) [R] Why is read_csv_arrow so much slower when using S3 path notation?

Carl Boettiger created ARROW-17597:
--------------------------------------

             Summary: [R] Why is read_csv_arrow so much slower when using S3 path notation?
                 Key: ARROW-17597
                 URL: https://issues.apache.org/jira/browse/ARROW-17597
             Project: Apache Arrow
          Issue Type: Bug
          Components: R
            Reporter: Carl Boettiger


Consider these two mechanisms for reading from a public bucket.  I was struck to see that using S3 path notation was consistently over 20 times slower than using the https address directly.  I could imagine a small overhead for using S3, but compared to other operations this seems something weird is going on here:



{code:java}
library(arrow)
targe <- s3_bucket("neon4cast-targets", endpoint_override="data.ecoforecast.org", anonymous=TRUE)

bench::bench_time({ # 58.6 seconds
  ex1 <- read_csv_arrow(targe$path("terrestrial_30min/terrestrial_30min-targets.csv.gz"))
})

bench::bench_time({ # 2.7 sec
  ex2 <- read_csv_arrow("https://data.ecoforecast.org/neon4cast-targets/terrestrial_30min/terrestrial_30min-targets.csv.gz")
})
 {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)