----- Original Message ----- From: "Vladimir Prus" <vladimir@codesourcery.com> To: <boost@lists.boost.org> Sent: Wednesday, November 04, 2009 4:55 PM Subject: Re: [boost] [build] Performance tests

vicente.botet wrote:

...

Hi,

I would like to execute some performance test with Boost.Build. Is there a way to force the execution of the tests without building the executables?

You should be able to do this:

exe hello : hello.cpp ; run-output hello.output : hello ; time hello.time : hello.output ;

The first metatarget just builds exe, as usual. The second runs the executable (capturing the output). The third records the time spend to run the executed.

You might need to 'import testing ; ' on top.

...

Are there some examples of performance tests for some Boost libraries?

I am not aware of such.

Hope this helps,

Thanks ofor the hint. I didn't know run-output and time. Are these commands documented? This allows me to get the time but in order to get again the time I need to force to build all with -a. I would like to build all the executables targets, and then be able to run performance tests several times. BTW, I need to pass some args when running the program. I do this now as

vicente.botet wrote:

----- Original Message ----- From: "Vladimir Prus" <vladimir@codesourcery.com> To: <boost@lists.boost.org> Sent: Wednesday, November 04, 2009 4:55 PM Subject: Re: [boost] [build] Performance tests

...

vicente.botet wrote:

...

Hi,

I would like to execute some performance test with Boost.Build. Is there a way to force the execution of the tests without building the executables?

You should be able to do this:

exe hello : hello.cpp ; run-output hello.output : hello ; time hello.time : hello.output ;

The first metatarget just builds exe, as usual. The second runs the executable (capturing the output). The third records the time spend to run the executed.

You might need to 'import testing ; ' on top.

...

Are there some examples of performance tests for some Boost libraries?

I am not aware of such.

Hope this helps,

Thanks ofor the hint. I didn't know run-output and time. Are these commands documented?

Unfortunately not.

This allows me to get the time but in order to get again the time I need to force to build all with -a. I would like to build all the executables targets, and then be able to run performance tests several times.

BTW, I need to pass some args when running the program. I do this now as

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

vicente.botet wrote: [sorry for previously posting an incomplete draft of this response]

...

You should be able to do this:

exe hello : hello.cpp ; run-output hello.output : hello ; time hello.time : hello.output ;

The first metatarget just builds exe, as usual. The second runs the executable (capturing the output). The third records the time spend to run the executed.

You might need to 'import testing ; ' on top.

...

Are there some examples of performance tests for some Boost libraries?

I am not aware of such.

Hope this helps,

Thanks for the hint. I didn't know run-output and time.

This allows me to get the time but in order to get again the time I need to force to build all with -a.

$ bjam -q perf ...patience... ...found 2444 targets... ...updating 5 targets... gcc.archive /sandbox/stm/branches/vbe/libs/stm/build/bin/gcc-3.4.4/debug/link-st atic/threading-multi/libboost_STM.a gcc.link bin/gcc-3.4.4/debug/threading-multi/perf_counter.exe testing.capture-output bin/gcc-3.4.4/debug/threading-multi/perf_counter.run testing.time bin/gcc-3.4.4/debug/threading-multi/perf_counter.time user: [perf_counter.run] 0.106000 system: [perf_counter.run] 0.122000 ...updated 5 targets...

I would like to build all the executables targets once, and then be able to run performance tests several times. Is this possible?

It's now possible -- using trunk version of Boost.Build. Add always hello.output ;

BTW, I need to pass some args when running the test program. I do this now as

alias dir_invalid : [ run stm : -bench rbtree -dir -threads 4 -inserts 100 : : : rbtree_dir_t4_i100 ] ... ;

How can I integrate run-output and time in a test suite?

You might want to try: run stm : -bench rbtree -dir -threads 4 -inserts 100 : : : rbtree_dir_t4_i100 time rbtree_dir_t4_i100.time : rbtree_dir_t4_i100.output ; You can also create a helper function, run-with-time, like so: rule run-with-time ( sources + : args * : input-files * : requirements * : target-name ? : default-build * ) { local t = [ run $(sources) : $(args) : $(input-files) : $(requirements) : $(target-name) ] ; local name = [ $(t).name ] ; time $(name).time : $(name) ; } Beware that the above is untested (but should work) - Volodya