Murthy:
Memory leak in the case of missing/wrong
ssl keys is identified and removed. Performance bottle necks due to nodeid
legacy support are removed wherever necessaay
After that full scale tests are conducted again with ~10000 virtual hosts for 72
hours. It is found that the queue turn-around time and accumulation of
samples/queue/sec is increasing with time and found to be approaching stable
after a very very long time. This is resulting in memory increase with time. It
is required to run the test for very long period say 5-6 days and then only
conclude on the stability of memory.
Yesterday also a test was conducted for 12 hours and it showed same behaviour.
In case the memory is not stable even after some period, ways to be found our to
improve database performance.
Email discussions are going on with Miro to resolve the issue.
Dinesh:
CCTracker status:
I've setup a development env here on my PC and deploying and testing the development done at BARC. Once everything works then I will discuss with Bill about the integration plan to deploy it here.
gc 12/07/06