Hi,
I have observed that the memory usage of the petsc mesh is much higher than my
previous code, if both were to be run serially.
For example, for a simple cubic box with 750,000 tetrahedral elements, my old
code takes about 200MB for the whole array, including all the mappings
required for later use such as the inverse connectivity table. For the same
mesh, my PETSc code takes about 4GB for the mesh alone.
The same can be found in the provided examples. I made a few changes to the
navierStokes code to output the virtual memory usage and got
./navierStokes -dim 3 -generate -structured 0 -refinement_limit 1e-6
109,283 elements, 139,030 edges , 21,523 vertexes
[0]:after mesh created:mem=574.46 MB
This is consistent with my Petsc code.
I understand that for the mesh to scale in parallel, extra information needs
to be stored. But the current cost seems too expensive. I am wondering if
there is a way to cut the memory usage for the mesh.
Thank you very much.
Shi
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20071031/c4f99042/attachment.htm>
