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
Currently, with doing all Lightroom API interactions on-device, we're using an extremely large amount of data per catalog-load. This is driven by the fact that we need to do album/catalog filtering on-device, forcing us to paginate over all assets, including the asset body. Anecdotally this is around 4.5MB/500 assets loaded.
Possible solutions:
Ask Adobe nicely to open up a search API
Implement a backend layer which would do the pagination & filtering in the cloud, saving on bytes over the wire
The text was updated successfully, but these errors were encountered:
jamiesanson
changed the title
Is there anything I can do RE data usage? 4.5MB/500 assets loaded
Investigate BFF API layer
Nov 28, 2023
Currently, with doing all Lightroom API interactions on-device, we're using an extremely large amount of data per catalog-load. This is driven by the fact that we need to do album/catalog filtering on-device, forcing us to paginate over all assets, including the
asset
body. Anecdotally this is around 4.5MB/500 assets loaded.Possible solutions:
The text was updated successfully, but these errors were encountered: