Azure 存储 - blob 版本控制如何影响列表操作？
Azure storage - How does blob versioning affect listing operations?
从microsoft docs开始，好像版本太多会影响上榜操作速度
Enabling versioning for data that is frequently overwritten may result in increased storage capacity charges and increased latency during listing operations. To mitigate these concerns, store frequently overwritten data in a separate storage account with versioning disabled.
创建新版本是否会进行列表操作或锁定某些内容？
SumanthMarigowda-MSFT 说的可能是List Blobs:
include={snapshots,metadata,uncommittedblobs,copy,deleted,tags,versions,
deletedwithversions,immutabilitypolicy,legalhold,permissions}
Optional. Specifies one or more datasets to include in the response:
-versions: Version 2019-12-12 and newer. Specifies that Versions of blobs should be included in the enumeration.
创建新版本不会执行列表操作，也不会锁定任何内容。只是如果您对一个 blob 进行大量更新，您将创建很多版本。
更多版本意味着增加容量费用。当您列出 blob 并包含版本时，更多版本意味着更长的上市时间。
从microsoft docs开始，好像版本太多会影响上榜操作速度
Enabling versioning for data that is frequently overwritten may result in increased storage capacity charges and increased latency during listing operations. To mitigate these concerns, store frequently overwritten data in a separate storage account with versioning disabled.
创建新版本是否会进行列表操作或锁定某些内容？
SumanthMarigowda-MSFT 说的可能是List Blobs:
include={snapshots,metadata,uncommittedblobs,copy,deleted,tags,versions, deletedwithversions,immutabilitypolicy,legalhold,permissions}
Optional. Specifies one or more datasets to include in the response:
-versions: Version 2019-12-12 and newer. Specifies that Versions of blobs should be included in the enumeration.
创建新版本不会执行列表操作，也不会锁定任何内容。只是如果您对一个 blob 进行大量更新，您将创建很多版本。
更多版本意味着增加容量费用。当您列出 blob 并包含版本时，更多版本意味着更长的上市时间。