I would like to get rid of the way JMeter is walking through all the
jars in lib/ext searching for GUI classes. On my machine (AMD Duron
800MHz) it takes 15 seconds from starting JMeter until the JMeter window
shows up which is quite annoying. I played around with what I called
plugins on the refactorings branch to speed this up. The way it is done
is not to search for classes in the jars but to register all known
JMeter GUI classes explicitly. Because JMeter is seperated into 7 jars I
needed a way to register the classes jar by jar and therefore added a
class to each of the jars which implements a Plugin interface and has
the responsibility to register all relevant classes. This is far from
being perfect but this way it takes only 7 seconds to start JMeter. This
is still too much but I know there is room for further improvement.
I would like to implement the plugins on the main branch now in the
following way:
- I make plugins out of the seven JMeter jars to register all the JMeter
classes explicitly
- therefore I would move the jars from lib/ext to a new plugin directory
- the mechanism to search all jars in lib/ext for GUI classes would
remain to make it easy for others to add their additional elements/GUIs
to JMeter without the need to worry about plugins (I assert that these
add-on jars will be small and therefore fast to search for classes)
Opinions, objections, improvements?
Oliver
smime.p7s
Description: S/MIME Cryptographic Signature
