Ben, I am looking forward to seeing you at the conference !
Performance wise, my profiling results have shown that dof-indices and shape function evaluations are a significant part of the residual evaluation but it is almost insignificant as compared to the nonlinear solve itself. This might be also because I do try, over-zealously sometimes, to do the solves matrix-free ! I do not think it is a bottle-neck yet but will keep you guys informed if this becomes important. Vijay On Sun, May 17, 2009 at 9:21 AM, Kirk, Benjamin (JSC-EG311) <[email protected]> wrote: > On 5/17/09 8:45 AM, "Roy Stogner" <[email protected]> wrote: > >> Anyway, right now optimizing FE calculations is not something libMesh >> does well, even to the extent it can be done with arbitrary elements. >> I'd bet that just vectorizing the fe_shape* function call API would >> give us a non-trivial performance boost. > > With a small amount of effort (seriously) I think we could cache all the > reference element values such that the underlying shape functions are > evaluated only once per (geometric element/finite element/quadrature order) > pairing. > > We do this to some extent now in that data are only reevaluated when the > geometric element type changes during iteration, but this could be pretty > often. > > with a little template trickery we could actually build static tables at > compile-time. if evaluating shape functions is a bottleneck in your app let > me know - it hasn't been a big priority at least for me. > > -Ben > > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
