You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 31, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 31, 2026. It is now read-only.
Do please consider properly externalising the http configuration so that it can be tweaked for high throughput systems. Especially when using storage.Client.from_service_account_json()
Right now, having to set _connection implies it isn't externalised. Unless the library is able to "auto-detect" the ideal configuration given large-files/low-throughput small-files/high-throughput average-files/average-throughput, I suggest you don't hide this.
changed the title [-]Google Cloud Storage Supports 1000 Writes Per Second By Default. Do you?[/-][+]Storage: Consider externalising http configuration[/+]on Apr 10, 2018
@sangramql There isn't an "obvious" design for this one.
@ravindranathakila I'm not clear on what you are thinking here. The _connection here doesn't hold any configuration which would affect how blob instances are uploaded / downloaded: it wraps an instance of an object supporting the requests.Session interface (normally a google.auth.transport.requests.AuthorizedSession instance).
The parameter which most affects "througput" is chunk_size, which can be passed to a Blob constructor (or set on it afterwards).
Activity
dhermes commentedon Dec 7, 2017
@ravindranathakila I'm unclear what the action item is for us here?
ravindranathakila commentedon Dec 8, 2017
Do please consider properly externalising the http configuration so that it can be tweaked for high throughput systems. Especially when using storage.Client.from_service_account_json()
Right now, having to set _connection implies it isn't externalised. Unless the library is able to "auto-detect" the ideal configuration given large-files/low-throughput small-files/high-throughput average-files/average-throughput, I suggest you don't hide this.
[-]Google Cloud Storage Supports 1000 Writes Per Second By Default. Do you?[/-][+]Storage: Consider externalising http configuration[/+]sangramql commentedon Jun 20, 2019
@tseaver please suggest the expected implementation and approach.
tseaver commentedon Jun 20, 2019
@sangramql There isn't an "obvious" design for this one.
@ravindranathakila I'm not clear on what you are thinking here. The
_connectionhere doesn't hold any configuration which would affect how blob instances are uploaded / downloaded: it wraps an instance of an object supporting therequests.Sessioninterface (normally agoogle.auth.transport.requests.AuthorizedSessioninstance).The parameter which most affects "througput" is
chunk_size, which can be passed to aBlobconstructor (or set on it afterwards).tseaver commentedon Aug 17, 2020
@ravindranathakila Please feel free to follow up / reopen if you can provide more clarity.
ravindranathakila commentedon Aug 18, 2020
chore: librarian release pull request: 20260113T144551Z (#1704)