[
> It would be good to build different visualizers inside
> JMeter. An alternate
> that I have been using for testing is to export data in the
> output file
> (File Visualizer) to Excel and generate different graphs from it. This
> gives me details into pivots, all kinds of line/bar graphs and all the
> other analysis features that excel provides. There were some
> changes that I
> made a few days back that allows all submit data to be stored
> on the output
> file. This can be extended to storing appropriate result data
> in the output
> file too. Let me know if it is required and I can work on
> getting it in.
I'll have to look at what you've done so far and get back to you. I think
my opinion is that the more the user can control the output of the File
Visualizer, the better. ]
Agreed. I remember adding a few extra options to the gui. If required we
can add more. The sample result can contain everything and the visualizer
writes whatever is setup by the user.
[>
> Secondly, is anybody working on testing EJB performance. I have been
> working a little on that end (building a visualizer and the related
> classes) and wouldn't like to duplicate the effort.
Not that I know of.]
Do you think it would be required by a lot of people out there? The code is
complex ;-( and I am still working on it.
[>
> I have mixed views about random Log4J statements spread throughout the
> code. It adds significant debugging capabilities for the
> developer of a
> class but may not be very useful for others using the
> classes. There is
> also a performance penalty associated with using these. Also
> there is the
> additional risk of code breaking because of the debug
> statements. In my
> perspective use them - but with a little bit of care. Would
> anybody like to
> recommend standards as to how to use these.
I just personally don't like them. I can deal, though. It's great having
other developers helping out and adding things I would never have thought
of. Maybe I could simply throw out some ideas for alternatives to log
statements:
1. Write unit tests instead of log statements if the purpose is to verify
the code is working right.
2. Run JMeter with a tool that allows you to step through the code if the
purpose is to learn how JMeter works or see the runtime values of
variables.
This is not always a better solution, but it should be considered.
Note, I'm not saying all logging is bad - just that some of it appears to
be
a clumsy way of doing one of the above.
-Mike]
-Tushar
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
