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
During the testing process of the isolate-path-env in #159, it has been found that the performance is poor when a group of objects is saved using noc.put_object within the cache.commit stage, especially when the internal write operations in op-env lead to a switch to hub mode for the object-map. This mode switch unavoidably generates a large number of sub object-maps, resulting in a time-consuming commit process.
Therefore, future optimizations should be considered.
The text was updated successfully, but these errors were encountered:
Below are a few possible optimization points currently under consideration:
Add batch operations in the noc interface
This is mainly for batch put_object operations, and the corresponding blob and meta layers also need to be optimized for batch processing.
Optimize the blob storage structure
This optimization is not only for improving write performance but also for read and storage improvements. Currently, objects are stored as individual files in the objects directory, which can lead to excessive disk files and performance issues when there are a massive number of objects. Consider using a pack-based storage approach or other similar methods to address this.
During the testing process of the isolate-path-env in #159, it has been found that the performance is poor when a group of objects is saved using noc.put_object within the cache.commit stage, especially when the internal write operations in op-env lead to a switch to hub mode for the object-map. This mode switch unavoidably generates a large number of sub object-maps, resulting in a time-consuming commit process.
Therefore, future optimizations should be considered.
The text was updated successfully, but these errors were encountered: