[petsc-dev] Adding support memkind allocators in PETSc

Jed Brown jed at jedbrown.org
Wed Jun 3 21:51:23 CDT 2015

Barry Smith <bsmith at mcs.anl.gov> writes:
>   Perhaps, and this is just nonsense off the top of my head, if you
>   had some measure of the importance of a vector (or matrix; I would
>   start with vectors for simplicity and since we have more of them)
>   based on how often it's values would be "accessed". So a vector that
>   you know is only used "once in a while" gets a lower "importance"
>   than one that gets used "very often". Of course determining these
>   vectors importances may be difficult. You could do it
>   experimentally, add some code that measures how often each vector
>   gets its values "accessed (whatever that means)/read write" and see
>   if there is some distribution (do this for a nontrivial TS example)
>   where some vectors are accessed often and others rarely. 

This is what I termed profile-guided and it's very accurate (you have
global space-time information), but super brittle when

Note that in case of Krylov solvers, the first vectors in the Krylov
space are accessed far more than later vectors (e.g., the 30th vector is
accessed once per 30 iterations versus the first vector which is
accessed every iteration).  Simple greedy allocation is great for this

It's terrible in other cases, a simple case of which is two solvers
where the first is cheap (or solved only rarely) and the second is
solved repeatedly at great expense.  Nested solvers are one such
example.  But you don't know which one is more expensive except in
retrospect, and this can even change as nonlinearities evolve.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150603/cb5d4d8e/attachment.sig>

More information about the petsc-dev mailing list