[
https://issues.apache.org/jira/browse/OAK-8551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917508#comment-16917508
]
Amit Jain commented on OAK-8551:
--------------------------------
{quote}Signed urls should be issued based on information in the NodeStore alone
with no network API calls.
{quote}
For cloud DataStores there will be *a* network call to get the URI from the
cloud provider. After reverting OAK-7998 in place that n/w call is down to only
that.
I implemented the change to isInlined from getReference in OAK-8578. The
comment
https://issues.apache.org/jira/browse/OAK-8578?focusedCommentId=16917497&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16917497
shows some improvements but numbers still bogged down by the actual create uri
call to the backend.
> Minimize network calls in cloud data stores (performance optimization)
> ----------------------------------------------------------------------
>
> Key: OAK-8551
> URL: https://issues.apache.org/jira/browse/OAK-8551
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob-cloud, blob-cloud-azure
> Affects Versions: 1.16.0, 1.10.4
> Reporter: Matt Ryan
> Assignee: Matt Ryan
> Priority: Major
>
> Oak cloud data stores (e.g. {{AzureDataStore}}, {{S3DataStore}}) are by
> definition more susceptible to performance degradation due to network issues.
> While we can't do much about the performance of uploading or downloading a
> blob, there are other places within the implementations where we are making
> network calls to the storage service which might be avoidable or minimized.
> One example is the {{exists()}} call to check whether a blob with a
> particular identifier exists in the blob storage. In some places
> {{exists()}} is being called where instead we could simply attempt the
> network access and handle failures elegantly, avoiding making an extra
> network call. In other places perhaps a cache could be used to minimize
> round trips.
> Another example is the higher-level {{getReference()}} call in
> {{DataStoreBlobStore}}. This asks the implementation for a {{DataRecord}}
> and then gets the reference from that, but in truth the data store backend
> can already obtain a reference for an identifier on its own. Asking for the
> {{DataRecord}} however requires a network request to get the blob metadata
> for the record.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
