On Mon, 8 Feb 2016, John Peterson wrote: > Also, remember that setting values in NumericVectors is already a fairly > indirect operation. For example, if you are using PETSc, the values are > cached and communicated only when the vector is closed.
We have seen speedup in some applications by using the vectorized NumericVector::insert() methods instead of NumericVector::set(). A few fewer virtual function calls made a small but noticeable difference. --- Roy ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
