Hello Rossi,
It seems it is the projection functions that are
computationally expensive. Would it be possible for you to run with the
PatchRecovery estimator, and see if that results in a similar performance ?
Thanks.
> On Apr 27, 2017, at 12:14, Vikram Garg wrote:
>
> Rossi,
Ok, I ran again the tests with different max_h_levels with the perflog enabled.
Let me know if you see anything here.
Thanks,
Simone
NO AMR
-
| libMesh Performance: Alive time=77.5482,
Rossi, yes compiling with perflog should give you all the details as in the
example.
On Thu, Apr 27, 2017 at 10:54 AM, Rossi, Simone
wrote:
> Dear Vikram,
> as in the examples, I am using the libmesh::KellyErrorEstimator.
>
> I’m compiling libmesh with the --enable-perflog option. Does it
Dear Vikram,
as in the examples, I am using the libmesh::KellyErrorEstimator.
I’m compiling libmesh with the --enable-perflog option. Does it automatically
give all the details you have listed in the example?
For the time being, I am attaching two perfLogs I had saved with only “coarse
scale”
Hello Rossi,
Two questions:
1) Which error estimator/indicator are you using to mark elements for
refinement ?
2) Can you send the perfLog output from libMesh ? You might need to
recompile libMesh with the option --enable-perflog.
Looks something like this:
