[tor-bugs] #13616 [Onionoo]: define jmeter testcase(s) ant ant task(s)

[Tor Bug Tracker & Wiki]

#13616: define jmeter testcase(s) ant ant task(s)
-----------------------------+-------------------------------
     Reporter:  iwakeh       |      Owner:  iwakeh
         Type:  enhancement  |     Status:  needs_information
     Priority:  major        |  Milestone:
    Component:  Onionoo      |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:  #13080
       Points:               |
-----------------------------+-------------------------------

Comment (by iwakeh):

 Concerning the test cases I would add more data, e.g. measure many request
 for different fingerprints or ip addresses (or ... or ...)  in order to
 avoid a bias when measuring the new retrieval methods.

 JMeter's scope is concurrent stress testing of the entire web application.
 If this is not intended at all, we should close this (#13616) issue.

 I think, 'response preparation performance measuring' should be a new
 issue.

 For a database benchmark I would suggest measuring data preparation
 using a simple benchmarking class that calls the code responsible for
 preparing
 a response directly. W/o any network or web app in between.

 This benchmarking class could be in the testing package. An ant task
 could be added for performing these benchmark tests. Thus, even ensuring
 later on that certain changes don't degrade performance.

 It might be even good to prepare a measurement class for json parsing and
 preparing in itself, in order to evaluate Gson replacements?

 What do you think?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13616#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online