Hi jukka
I asked in the mailing list what's the right way to go for extending
jmeter and a user pointed me to a useful manual for plugin development.
I was able to extend the java protocol to run chain commands :), so it
was not so difficult after all. I'll upload a proof of concept of
jcr-chains and jmeter-chains to jira asap, hopefully this weekend.
BR,
edgar
Edgar Poce wrote:
Hi jukka
I've wanted to do performance testing for some time but I was quite
busy. In the meantime I gave it a couple of thoughts I'd like to share.
I'd like to achieve two goals:
1. create jcr commands (e.g. "AddNodeCmd", "SetPropertyCmd", "SaveCmd")
which can be combined into a chain. I think this would be useful also
for manipulating the repository either declaratively or programatically.
2. Make the commands accessible to jmeter in order to build custom test
plans and do performance testing.
The first part doesn't seem too hard, it can be implemented with commons
chain. The API is rather simple. In regard to the second goal, I think
it will be a little harder. I used jmeter a few times but I didn't dive
into the code til now. My first impression is that we could extend the
java protocol or create a new protocol for running chain commands.
If you think it's a good approach I volunteer to prepare a set of
commands, actually I already made a few :).
BR,
edgar
Jukka Zitting wrote:
Hi,
Now that the JCR API is final I'd like to focus on improving the
non-functional aspects of the JCR-RMI extension. To start with I'm
planning to do some performance and scalability benchmarking of
Jackrabbit both with and without the RMI layer.
Are there any existing performance benchmarking tools (in addition to
the 1mn write test discussed earlier) out there? I'd much rather work
with an existing codebase than write my own from scratch.
BR,
Jukka Zitting
