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, the RAG workspaces dashboard provides metrics on the file size of the data in the RAG workspace, the number of Vectors, etc.
As it stands today, the file size metric is calculated as files are added, increasing the storage amount, but don't take into account storage consumed for the vector collections.
While the metric may be accurate to the files uploaded, it can create misleading assumptions about how large the data footprint actually is. In my case, I have over 2M vectors generated from website crawling, which has led to my OpenSearch collection to be ~200GiB, but I have uploaded 0 files, so my workspace shows a file size of 0MB.
The metric should either have verbiage to better describe what is included OR expand the metric to be inclusive of the vector collection sizes.
The text was updated successfully, but these errors were encountered:
Thanks for reporting this.
We will improve the description on the metric and we will try to work on providing a comprehensive estimate of the total storage size used.
Currently, the RAG workspaces dashboard provides metrics on the file size of the data in the RAG workspace, the number of Vectors, etc.
As it stands today, the file size metric is calculated as files are added, increasing the storage amount, but don't take into account storage consumed for the vector collections.
While the metric may be accurate to the files uploaded, it can create misleading assumptions about how large the data footprint actually is. In my case, I have over 2M vectors generated from website crawling, which has led to my OpenSearch collection to be ~200GiB, but I have uploaded 0 files, so my workspace shows a file size of 0MB.
The metric should either have verbiage to better describe what is included OR expand the metric to be inclusive of the vector collection sizes.
The text was updated successfully, but these errors were encountered: