Memory Monitor

[Guyme]

Why : Have a single component that knows the memory status of the system. Know the status for each CF as a reporting and decision support for other features

what: Track both clean and dirty memory consumption per CF The memory monitor should register each CF during build and remove it during destroy The memory monitor should be able to calculate when needed the clean and dirty and flush pending memory size for each CF The memory monitor should have a method to report individual CF status and system wide status on clean, dirty, sum User interface for getting this report - logs

Who : reporting and monitoring. decision support for other features (clean \ dirty \ quota managers)