alex
do you mean that you execute the system and keep trace. or this is just static analysis.
Stef
On May 6, 2011, at 5:48 PM, Alexandre Bergel wrote:
Hi!
I have been working on a new profiler to reduce the amount of candidates when analyzing a
Smalltalk project. The idea is to run the test to know exactly what are the methods that
are invoked.
I would like you to try my implementation.
With Mondrian, the standard candidates operator produces 27,890 candidates for all the
methods. Using the profiler, it is reduced to 9,828. The amount of candidates is
significantly reduced.
Below two screenshots of a complexity blueprint. I made it on Arki. One with the normal
candidates, and one with the profiling.
<ArkiWithoutProfile.png><ArkiWithProfile.png>
Go to the the squeaksource project ArchitectureMonitor. There is a configuration in it.
Load the last version. Then you should have the option:
<Screen shot 2011-05-06 at 11.44.41.png>
I quickly worked on this, so it may be that it contains some error. I would like to know
whether you like this approach or not.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch