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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#13616: define jmeter testcase(s) and 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):

 Replying to [comment:9 karsten]:
 >
 > I wonder if we can use `out/summary` as input to automatically generate
 as many query samples as we need.
 Yeah, this seems the right way to do the benchmarking. In addition, we
 shouldn't forget
 searches without any results.

 >
 > That could be useful, though it's quite specific.  There's an assumption
 in that that Gson is the performance bottleneck, ...
 I don't assume that Gson is a performance bottleneck, in the opposite. But
 it has its quirks (e.g.
 html-escapes) and if at some point there is need and time to use a
 different json-solution, it
 might be good to at least get the same performance from the new solution.


 >  - Make room for performance tests somewhere in `src/` and write a
 separate Ant task to run them.
 I'll start with this one.

 >
 >  - Take an `out/summary` file as input and generate good sample requests
 for a `RequestHandler` performance test class.  Also write that test
 class.
 >
 >  - Write a performance test class for `ResponseBuilder`, probably
 requiring a successful run of the hourly updater to populate the `out/`
 directory.
 >
 >  - Write another performance test class for `DocumentStore` that takes a
 populated `status/` and `out/` directory as input and performs a random
 series of listing, retrieving, removing, and storing documents.  Ideally,
 the test class would make sure that the contents in both directories are
 still the same after running the test.
 >
 > Plenty of stuff to do here.  Want to help getting this started?
 Sure :-)

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13616#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs