Skip to content

Why the solvers provided by petsc run much slower than that provided by matlab itself #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RGQTJU opened this issue Aug 2, 2021 · 0 comments

Comments

@RGQTJU
Copy link

RGQTJU commented Aug 2, 2021

Thanks for your great work! What you did is exactly what I'm looking for!
I have added your work into my work, and I can also reproduce the example you provided in readme. But it runs quite slowly.
The following is how I build the program.
cd petsc4m;
startup;
build_petsc('-I/data2/DG/RGQ/ThirdParty/mpich/include','-omp'); %Here, the path to the head file of mpich is appointed
%explicitly, or the program will hault with error that mpi.h can't be found;
%'-omp' is also included since my program runs on a cluster with 72
% cores, and the environment variable OMP_NUM_THREADS is set to
% be 72.
init_petsc;

I run a test case after initialization of the program. The time elapsed is 232.30 seconds for the direct solver provided by matlab,
while it takes 1478.16 seconds when use SuperLU as a direct solver. And the time is even much longer for other solvers provided
in the readme file.
Do you have any idea about this?
Thanks in advance!
Best regards!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant