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
As a table format, Lance plays a crucial role in data storage and management for AI data. A comprehensive metrics system is essential in monitoring table formats, diagnosing health status, and performance-oriented governance. This is fully reflected in Apache Iceberg.
Apache Iceberg introduced metrics reporting1. It exposes some metadata and statistical information of core table operations (such as Scan/Commit) in the form of metrics. This ensures that these core pieces of information are not hidden beneath the iceberg.
In terms of its uses, with the external exposure of these metrics, we can do many things.
Monitoring: Includes some indicators related to load and performance. Third parties can provide some insightful dashboards based on these indicators 24;
Diagnosis: Based on monitoring, we can provide some incremental value. One of them is the diagnosis of some performance issues, which will assist in optimizing layout or performance;
Optimization: Based on the provided indicators, we can optimize performance at both the read and write ends.
The text was updated successfully, but these errors were encountered:
I think we're very much in favor of adding additional metrics. I had an initial start at this here; #3075 but I'm not sure if I'll get back to it soon. I was planning on adding some storage statistics soon as well.
I guess this issue itself is a little broad though. Is there a particular standard you are looking for? Is this something you are hoping to work on?
As a table format, Lance plays a crucial role in data storage and management for AI data. A comprehensive metrics system is essential in monitoring table formats, diagnosing health status, and performance-oriented governance. This is fully reflected in Apache Iceberg.
Apache Iceberg introduced metrics reporting1. It exposes some metadata and statistical information of core table operations (such as Scan/Commit) in the form of metrics. This ensures that these core pieces of information are not hidden beneath the iceberg.
In terms of its uses, with the external exposure of these metrics, we can do many things.
The text was updated successfully, but these errors were encountered: