New BigQuery pricing 'tiers' -


according pricing page, new tiered pricing model introduced bigquery on january 1st 2016.

we'd able predict cost implications may have our applications. we've taken @ json response of our more complex queries see 'tier' has been assigned it.

the billingtier tier visible in json response.

200 ok - show headers - {   "kind": "bigquery#job",   [...]   "totalbytesprocessed": "45319172942",   "query": {   "totalbytesprocessed": "45319172942",   "totalbytesbilled": "45319454720",   "billingtier": 1,   "cachehit": false }  

is default tier assigned (tier 1) until new pricing model kicks in on jan 1st 2016, or true indication of tier assigned query?

the billingtier field true indicator of tier assigned query according our upcoming pricing structure. if field set 1, query billed @ current (tier 1) rates under new pricing structure.

note billing tier computed separately on each invocation of query, there's no strict guarantee same query fall in same billing tier. i'd recommend spot-checking reasonable sample of queries general sense of workload fall under new pricing structure.


Comments

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -