We are working hard on the next update of the Analyzer.
This new update will be aimed at improved memory management.
This could especially be of interest to those of you that are working with large solutions and or more repositories.
However, it does not stop after that update. So, we are also thinking of new functionality for the Analyzer and would like you, our (potential) user, to give you opinion or add suggestions.
Somehow deal with memory requirements when scanning databases… Perhaps use a hard disk cache for the process? Right now it takes over a gigabyte of memory to just scan my database (admittedly it is big). But the end result on my PowerBook, unfortunately for this GREAT program, is that it is useless (and I only have a PowerBook).
While working on that cache thing I was thinking of what you mentioned about loading servers.
The next update will give you preferences to load servers and scripts on startup or when you need them.
That should be an improvement.
When you want we could introduce a separate update for that.
Another thing is that you can already disable a server. By disabling the server its contents will not be loaded.
I am not sure how Analyzer scans databases, but it seems it must be possible for Analyzer to get the information it needs without the huge memory overhead.
Or, perhaps make the information persistent across uses?
But it seems it must be possible for Analyzer to get the information it needs without the huge memory overhead
That is a little ‘lightfooted’ assumption
Persistance is in the corner of caching and you know the answer to that one.
BTW making The analyzer persistant between uses is far less ideal because I can not imagine your repository has really static information and thus refreshes will be necessary…
