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
The Storage gRPC service, when checking for new files, first gets the number of new files to allocate a vector of the correct size, and then basically executes the same query again, this time dumping the actual data into the vector. The reason is that soci expects the vector to have a sufficient size.
To solve this, we could try and use a cursor instead, since we know we will be getting fixed size chunks there. Then we avoid doing the same work twice.
The text was updated successfully, but these errors were encountered:
The Storage gRPC service, when checking for new files, first gets the number of new files to allocate a vector of the correct size, and then basically executes the same query again, this time dumping the actual data into the vector. The reason is that soci expects the vector to have a sufficient size.
To solve this, we could try and use a cursor instead, since we know we will be getting fixed size chunks there. Then we avoid doing the same work twice.
The text was updated successfully, but these errors were encountered: