Tonyar / xjperf

Automatically exported from code.google.com/p/xjperf
0 stars 0 forks source link

Save configuration profile(enhancement) #4

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. It would be nice to allow user to save configuration base on config
file.  Sometimes I need to save the configuration so I don't need to retype
all the configurations again.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by chad...@gmail.com on 25 Sep 2008 at 9:09

GoogleCodeExporter commented 8 years ago
I vote for addressing this one as well.  At the very least I would love to be 
able to
define an assortment of variables on the CLI that get passed to jperf at startup
(with that bat or sh file).  I'd like to be able to define my server, port, 
transmit
time, output format, testing mode and sub-options, etc.  I'd like to stick 
jperf in
the hands of fairly non-computer savvy field techs and have it be 
pre-configured at
startup with the options I want them to use.  This doesn't strike me as too 
difficult
of a thing to do if we're only passing arguments in on the CLI.  Adding the 
ability
to save a settings file or profile would take more doing of course but I don't
personally need those options.

I vote for this one!

Original comment by routers...@gmail.com on 19 Mar 2009 at 7:52

GoogleCodeExporter commented 8 years ago
feature implemented in JPerf 2.0.2

Original comment by nicolas....@gmail.com on 5 May 2009 at 9:14