On Jun 14 2016, Brandon <[email protected]> wrote:
> 1) How does S3QL work with using Google Cloud's "Nearline" storage
> option?
I don't know anything about "Nearline", but I'll try to answer your
questions:
> Does it write all the data once and just forget it - that is, not needing
> to access any of the data again to any extent that would rack up
> considerable charges?
As long as you're not trying to read or write the data, S3QL is not
going to request it from the backend.
However, S3QL will periodically upload its metadata (by default every 24
hours). Other than that, it just reads the metadata on mounting, and
writes it on unmount.
If there is a way to enable "Nearline" only for some object, you should
be good if you enable it for everything starting with "s3ql_data". These
objects are only ever accessed as a result of user action.
> In general I am unfamiliar with the billing model for
> reading and writing data, and how S3QL would work for both writing data
> once and forgetting it except for listing (ls) the files now and then (like
> for a backup), and for accessing data frequently. What is PUT/GET request
> usage for this amount of data?
Every file requires (filesize)/(object size) PUTs to store. Same for
retrieval.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
