Re: [Boost-bugs] [Boost C++ Libraries] #1560: Performance testing with boost::test

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #1560: Performance testing with boost::test
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-01-21 19:54:47


#1560: Performance testing with boost::test
----------------------------------------------+-----------------------------
  Reporter: John Pavel <jrp_at_[hidden]> | Owner: rogeeff
      Type: Feature Requests | Status: reopened
 Milestone: To Be Determined | Component: test
   Version: Boost Development Trunk | Severity: Optimization
Resolution: | Keywords:
----------------------------------------------+-----------------------------
Changes (by jrp at dial dot pipex dot com):

  * status: closed => reopened
  * resolution: wontfix =>

Comment:

> These macros have number of issues:
>
> 1. Problem domain is unclear. What exactly are you trying to test?

 I am just trying to do some array manipulation using a range of different
 packages.

> 2. Number of parameters are using. none of them is configurable. It's
> unacceptable in generic solution

 That is also a problem for me, as I would like to try different array
 lengths.

> 3. boost:;timer is not a best device for use to measure performace.

 Yes.

> I do plan to introduce some performace testing toosl. But these macro
> doesn't look right right way to go

 I agree. What I need is something that:

  - time the running of a test case (that is already there, if the right
 logging is enabled, although the output is messy)
  - can distinguish between fixture setup time and time to run the test
  - can be set to count the number of times that a test must be run before
 a specified period elapses
  - give an indication of whether the test takes a linear amount of time
 with respect to the test parameter (eg, the length of the array)

--
Ticket URL: <http://svn.boost.org/trac/boost/ticket/1560#comment:2>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.


This archive was generated by hypermail 2.1.7 : 2017-02-16 18:49:57 UTC