Monsters in Memory !
Can you imagine idle java processes eating away 70% of your Operating system RAM share. In our Content management system built on a propriety product suite, we were taken by surprise to realize that it is a baggage from the product architecture. However, I must not point fingers at the vendor as they have mentioned in their product manuals to disable the non-essential services to be disabled in the early phase it self. But we have left with no such choice now. May be this kind of elasticity & flexibility is desirable any product in the days forward.
Our content management system follows an event based consumer - subscriber model for sharing the events across different content related services such as Workflow, We found that our event subsystem and the associated small relational database related Java Processes are alive all the time. That must be the rationale behind keeping these processes alive.
Along with it, we could find a Servlet and Search agent built on Java API's alive all the time. All the villains are identified. But not able to keep them behind the bars as they are essential for the system's standard behavior and as-is status. This makes me think and highlight that Content management systems are still memory and event intensive model. I must say that this +ECM has derived lot of base model from the standards of Version Control systems and relational data models. What made it unique was the OS level coupling it has achieved by adding a lot of modifications on the OS registries and device drivers at the firmware level .. Anyway I am just curious what will these bunch of monsters will do tomorrow as the story continues. Data Diary and Data Dilemma continues ...
PS: All views are my own
