Live data from Hacker News

Introducing Google Cloud Storage Nearline

googlecloudplatform.blogspot.com

21–30 of 188 posts

Re: Introducing Google Cloud Storage Nearline

#21
post #19
post #17

Isn't the price a little high? $10/TB/mo is the same as Dropbox, and this has a lot fewer features than Dropbox.

It's a bit apples to oranges comparison. Dropbox is a consumer product, like Google Drive. Nearline is targeted to app developers and enterprises

Exactly, so why would the lower-level service aimed at big slow transfers be more expensive than a full-featured product?

Re: Introducing Google Cloud Storage Nearline

#24
post #17

Isn't the price a little high? $10/TB/mo is the same as Dropbox, and this has a lot fewer features than Dropbox.

I understand the downvotes (they're very different services, and Dropbox prices can be very low because you're paying for capacity not usage - case in point I'm currently using 25 gigs but paying for a terabyte) but honestly - that's an interesting point... anyone want to write an API?

Re: Introducing Google Cloud Storage Nearline

#25
post #12
post #8

So how is this implemented? Spun-down disk drives?

My guess would be disk drives that are otherwise used for I/O intensive purposes, and where there's tons of unused/wasted space. 4MB/s is only around 4% of the bandwidth of a modern 1TB hard disk.

Why would they want to risk the performance of the I/O intensive disks?

Re: Introducing Google Cloud Storage Nearline

#26
post #4

from the documentation: "You should expect 4 MB/s of throughput per TB of data stored as Nearline Storage. This throughput scales linearly with increased storage consumption."

That would mean that if you had about 1TB stored it would take more than 3 days to retrieve it (with an initial 3 second delay before it starts).

[deleted]

Re: Introducing Google Cloud Storage Nearline

#28
post #12

Earlier quoted context omitted.

My guess would be disk drives that are otherwise used for I/O intensive purposes, and where there's tons of unused/wasted space. 4MB/s is only around 4% of the bandwidth of a modern 1TB hard disk.

Why would they want to risk the performance of the I/O intensive disks?

With a 3s average response time and presumably replication across multiple disks, you've plenty of scope to schedule requests in a way that they won't affect performance.

In 3s on one disk you can do roughly 5k seeks and read up to 300MB. They only need to do 1 seek and read 4MB.

Re: Introducing Google Cloud Storage Nearline

#29
post #21
post #19

Earlier quoted context omitted.

It's a bit apples to oranges comparison. Dropbox is a consumer product, like Google Drive. Nearline is targeted to app developers and enterprises

Exactly, so why would the lower-level service aimed at big slow transfers be more expensive than a full-featured product?

SLAs on availability/durability & guaranteed throughput..

Re: Introducing Google Cloud Storage Nearline

#30
post #21
post #19

Earlier quoted context omitted.

It's a bit apples to oranges comparison. Dropbox is a consumer product, like Google Drive. Nearline is targeted to app developers and enterprises

Exactly, so why would the lower-level service aimed at big slow transfers be more expensive than a full-featured product?

The full-featured product is $10 regardless of how much storage you're using. If my requirements are for 1GB, then my price is $0.01 a month.
Post reply on HN