Getting file from S3 and copying to stream is taking ages

By -

I am trying to get a 3MB file from a S3 bucket and copying it to a MemoryStream because I will need to check what is inside this file at a later point. However, when CopyToAsync gets called, it takes at least 1 minute to complete.

Here's the code I have right now:

using var s3Object = await _client.GetObjectAsync(getRequest);

var ms = new MemoryStream();

// taking ages
await s3Object.ResponseStream.CopyToAsync(ms);

return ms;

I tried to use the transfer utility to open the stream or download the file but it takes roughly the same amount of time.

Am I doing something wrong? Is there a different approach?

From my understanding the s3Object variable is receiving metadata about the s3 object + the beginning of the stream of the mentioned file. So when CopyToAsync gets called it actually "downloads" the complete file.

The file looks something like this:

DEPT    .M                                      :1     Index curve
GR      .GAPI                                   :2     L05-07
DT      .US/F                                   :3     L05-07
RHOB    .G/C3                                   :4     L05-07
DRHO    .G/C3                                   :5     L05-07
NPHI    .V/V                                    :6     L05-07
~Ascii Log Data
      63.1000   -999.250000   -999.250000   -999.250000   -999.250000   -999.250000
      63.2000   -999.250000   -999.250000   -999.250000   -999.250000   -999.250000
      63.3000   -999.250000   -999.250000   -999.250000   -999.250000   -999.250000
      63.4000   -999.250000   -999.250000   -999.250000   -999.250000   -999.250000
      63.5000     11.094475   -999.250000   -999.250000   -999.250000   -999.250000
      63.6000     11.473166   -999.250000   -999.250000   -999.250000   -999.250000
      63.7000     12.066418   -999.250000   -999.250000   -999.250000   -999.250000
      63.8000     12.302490   -999.250000   -999.250000   -999.250000   -999.250000
      63.9000     12.272800   -999.250000   -999.250000   -999.250000   -999.250000
      64.0000     11.762026   -999.250000   -999.250000   -999.250000   -999.250000
      64.1000     10.414513   -999.250000   -999.250000   -999.250000   -999.250000
      64.2000      9.588345   -999.250000   -999.250000   -999.250000   -999.250000

Thanks for any help!



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more