Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you're seeing 21Mbps per object and running around 20 objects at a time, you're getting around 420Mbps throughput from one machine. On the other hand, if you're seeing 21Mbps total, that suggests that you're probably getting throttled pretty heavily somewhere along the path.</p> <p>I'd suggest that you may want to use multiple smaller instances to spread the requests across multiple IP addresses; for example, using 4 n1-standard-2 instances may result in better total throughput than one n1-standard-8. You'll need to split up the files to transfer across the machines in order to do this.</p> <p>I'm also wondering, based on your comments, how many streams you're keeping open at once. In most of the tests I've seen, you get diminishing returns from extra threads/streams by the time you've reached 8-16 streams, and often a single stream is at least 60-80% as fast as multiple streams with chunking.</p> <p>One other thing you may want to investigate is what download/upload speeds you're seeing; copying the data to local disk and then re-uploading it will let you get individual measurements for download and upload speed, and using local disk as a buffer might speed up the entire process if gsutil is blocking reading from one pipe due to waiting for writes to the other one.</p> <p>One other thing you haven't mentioned is which zone you're running in. I'm presuming you're running in one of the US regions rather than an EU region, and downloading from Amazon's us-east S3 location.</p>
    singulars
    1. This table or related slice is empty.
    1. POSpeeding up S3 to GCS transfer using GCE and gsutil
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USE. Anderson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSpeeding up S3 to GCS transfer using GCE and gsutil
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your response.
      singulars
      1. PO
      1. USSeb
    2. COI was considering running it on multiple instances in the first place, so I think that I will go with your advice and make each of those instances smaller/cheaper since they will probably achieve more per dollar spent. I may not go on an in depth investigation on the up/download speeds of the instances because of time constraints and the low overall cost of the transfer with current performance, but I will look into the zones of the GCE machines I use. Do you have any idea of how I can find out the GS zone I will be uploading to?
      singulars
      1. PO
      1. USSeb
    3. COSorry, I missed this response; you can choose the location that a Google Cloud Storage bucket will be located in when creating the bucket: https://developers.google.com/storage/docs/concepts-techniques#specifyinglocations You can find the location of an existing bucket with the command: `gsutil ls -L -b gs://my-bucket/`
      singulars
      1. PO
      1. USE. Anderson
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload