On Sat, Jan 16, 2016 at 7:12 AM, Griffith, Boyce Eugene <
[email protected]> wrote:

>
> On Jan 16, 2016, at 12:34 AM, Bhalla, Amneet Pal S <[email protected]>
> wrote:
>
>
>
> On Jan 15, 2016, at 5:40 PM, Matthew Knepley <[email protected]> wrote:
>
> I am inclined to try
> Barry's experiment first, since this may have bugs that we have not yet
> discovered.
>
>
> Ok, I tried Barry’s suggestion. The runtime for
> PetscOptionsFindPair_Private() fell from 14% to mere 1.6%.
> If I am getting it right, it’s the petsc options in the KSPSolve() that is
> sucking up nontrivial amount of time (14 - 1.6)
> and not KSPSetFromOptions() itself (1.6%).
>
>
> Barry / Matt / Jed, if we were using KSPReset here and reusing KSPs, would
> that also bypass these calls to PetscOptionsXXX?
>

No, we have to fix KSPSolve(). We will do it right now.

  Thanks,

    Matt


> Thanks,
>
> -- Boyce
>



-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener

Reply via email to