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
Hello! I was curious if there was a reason gcsfs uses aiohttp with the JSON API to query GCS rather than using the Google Python client which calls the gRPC API. AFAIK the gRPC API is a lot more efficient.
The text was updated successfully, but these errors were encountered:
I don't think grpc-async was a thing when this repo switched to async.
Honestly, I doubt for the size of the encoded messages, it makes any difference at all, and actually json is pretty well optimized for python (whereas protobufs are certainly not). Any bytes payload (i.e., file down/uploads) would be the same in either model.
Hello! I was curious if there was a reason gcsfs uses
aiohttp
with the JSON API to query GCS rather than using the Google Python client which calls the gRPC API. AFAIK the gRPC API is a lot more efficient.The text was updated successfully, but these errors were encountered: