Details
-
Bug
-
Resolution: Fixed
-
Major
-
4.5.0
-
None
-
Untriaged
-
Unknown
Description
Build 2009
Not sure if this is something that we can improve, but it would be helpful to see the data size growing as the index is being built. Especially if we are building an index that may not fit within the RAM available...the user now needs to monitor the underlying system.
See screenshot...this index is taking up >13GB of RAM already.
Attachments
For Gerrit Dashboard: MB-19020 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
62423,2 | MB-19020 memdb/stats: Retrieve aggregated stats | unstable | indexing | Status: MERGED | +2 | +1 |
62554,5 | MB-19020 memdb: Fix pointers per node stats aggregation | unstable | indexing | Status: MERGED | +2 | +1 |