|Re: [eigen] Help needed to run a benchmark on many machines|
[ Thread Index | Date Index | More lists.tuxfamily.org/eigen Archives ]
Hi,I have a few questions regarding the tests...a) Do you need more tests on other machines?
b) Do the machines/devices really matter, or are only the sizes of the data caches important?
c) Do we actually need to test user CPU times as opposed to wall times?
I asking about b) because of your suggestion to provide tables per device and not based on the device's cache configurations.
Regarding c), boost has a special clock in its chrono implementation (see here: http://goo.gl/ETH4Bk). Maybe there is a profiling pro over here who can shed some light on this?
Regards,HaukeOn Wed Feb 18 2015 at 8:57:15 PM Benoit Jacob <jacob.benoit.1@xxxxxxxxx> wrote:Hi Benoit,
I am running the test right now. I needed to add a few changes (see
attached main.cpp). Classical windows specific stuff.I've looked at the diff between your file and mine, but it's very big because of many whitespace/style changes.If you can send me a minimal diff, I'll happily apply it.
I also needed to change std::min<SizeType> to std::min<Index> in the
I will let you know once the test finishes.
On Wed, Feb 18, 2015 at 5:58 PM, Benoit Jacob <jacob.benoit.1@xxxxxxxxx> wrote:
> Hi List,
> I'm looking into tuning Eigen's matrix product blocking parameters on
> various machines. That involves actually measuring the impact of different
> parameter values on performance. The tracking bug for this effort is
> I'm attaching a benchmark to this email. It tests all sorts of matrix
> product sizes with all sorts of blocking parameters, and outputs both a
> complete log and a table that might be what we need to directly provide
> Eigen with.
> It would be very helpful if some people could help me run it on different
> machines. It runs at least on:
> - GNU Linux
> - Android
> - Mac
> If you run it, please record its output into a text file and send it back to
> me together with some description of your device (e.g. "nexus 6"). The
> benchmark already records some hardware info such as /proc/cpuinfo on linux.
> Please also tell me your Eigen changeset, compiler and command line.
> Compilation instructions:
> - most important: please use today's devel branch of Eigen - must have the
> patch from http://eigen.tuxfamily.org/bz/show_bug.cgi?id=958 .
> - c++11 mode
> - on intel, please compile with -mavx if available
> - on ARM, please compile with -mfpu=neon-vfpv4 if available, otherwise
> -mfpu=neon for older devices. DO NOT pass a -march flag as that triggers
> compiler bugs spilling registers.
> - on ARM, bonus points if you can also apply the patch from
> http://eigen.tuxfamily.org/bz/show_bug.cgi?id=955 - not necessary but
> Example desktop command line:
> c++ -mavx -DNDEBUG -O3 --std=c++0x benchmark-blocking-sizes.cpp -o b -I
> ../eigen && ./b | tee log-blocking-sizes-mac
> Example Android command line:
> $CXX $SRC -o $EXE -save-temps \
> -O3 -DNDEBUG \
> --std=c++0x -Wall -Wextra -pedantic \
> -fPIE -pie -mfpu=neon-vfpv4 -mfloat-abi=softfp \
> -I $HOME/eigen
|Mail converted by MHonArc 2.6.19+||http://listengine.tuxfamily.org/|