public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrea Arteaga <andyspiros@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] Benchmarking suite - Report 8
Date: Mon, 18 Jul 2011 02:58:16 +0200	[thread overview]
Message-ID: <CAPtnn5GCnq57JS9MDOZu6ZoZ83jvL6U4e=KmV9xX8HMO=gGTeA@mail.gmail.com> (raw)

A very short log of what has been done during the last days. I am
working on the PBLAS and ScaLAPACK benchmarks, which is a very
challenging topic, because it is very difficult to debug such
applications.

* I changed some parts of the BTL framework, adapting it to the
distributed memory benchmarks. This has required writing two new
perfanalyzers -- one for the root process, one for the other (node)
processes. The nodes do not perform any measurement, while the root
process broadcasts the needed informations, measures the time and
manages the output (both std{out,err} and resulting file).

* I added a BLACS library that provides an useful interface which
scatters and gathers matrices and vectors. I also added a PBLAS
library that inherits the BLACS one and will support the most common
operations (at the moment just the parallel matrix-vector
multiplication).

* I added an action for the parallel matrix-vector multiplication
which makes use of the two described interfaces.

The matrix-vector multiplication is a case study for now. If
everything goes fine (and it seems so, now), then more actions will be
provided, for both PBLAS and ScaLAPACL, which share the same concepts.
I plan to have tomorrow a working (but incomplete) Python module for
PBLAS, too.

Milestones for the next week:
* Having working PBLAS and ScaLAPACK modules
* Do some benchmarks using these modules and publish the results
* Start the implementation of the advanced FFTW benchmarks, as
previously described

Best regards
Andrea Arteaga



                 reply	other threads:[~2011-07-18  0:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPtnn5GCnq57JS9MDOZu6ZoZ83jvL6U4e=KmV9xX8HMO=gGTeA@mail.gmail.com' \
    --to=andyspiros@gmail.com \
    --cc=gentoo-soc@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox