- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
when using pardiso on an upper triangular symmetric matrix of dimension 130,00 x 130,000 with 1,000,000 non-zeros it needs about 15 sec for a factorization, which is very slow compared to cholmod(suitesparse) 0.3 sec.
Further on large matrices, say >1,000,000 x >1,000,000 pardiso is so unbearable slow that it becomes unusable, whereas cholmod(suitesparse) can easily cope with the problem.
Is there any way to speed up pardiso? I figured that it gets stuck at the analysis stage.
I am using oneapi version 2021.2.0 on linux, kernel version 5.16.
Thanks
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The only way to speed up the reordering stage is by trying the OpenMP version of Metis (iparm[1]=3).
wrt to factorization performance against cholmod -- here make sense to share the case to check the behavior on our end.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'll make an example.
Question is how I can get he matrix to Intel? My current best example matrix with 12M rows/columns and 500M elements needs 11GB on disk!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You could upload the case anywhere ( google drive as an example) and give us the link by the private channel into this forum or directly via email ( Gennady.Fedorov@intel.com). And please add the driver which will write this matrix and run the solver with your parameters. It will essentially save the reproducing time.
-Gennady
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have emailed you a link for downloading an archive with matrix and driver.
The example also reproduces the observation from this thread https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/omp-warning-when-using-pardiso-and-metis-threaded-version/td-p/1363562
Thanks for looking into this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
@Gennady_F_Intel wondering whether you had the time yet to look into the example provided?
I just installed oneapi 2022.0.2, and all the described problems remain, even the omp_nested warning from this thread
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am very sorry, Karl. I missed this thread and will do it asap.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Gennady,
I responded to your email some time ago pointing out that there must be an issue at your side reading the sparse array in binary.
Is there any update on this?
Best
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Karl,
I responded by email to you on this matter.
The reordering performance problem has been reproduced on our end and escalated against the Sparse Solver Team.
We will keep this thread updated in case of any updates.
thanks,
Gennady
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I had contacted the pardiso team about this problem as well, and according to their test and a test library they provided to me the problem does not affect the most recent pardiso version.
Does Intel have any plans for updating pardiso?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Karl,
I just want to let you know that the team is still investigating this issue.
We will let you know once we find out the issue.
Best regards,
Khang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Karl,
The issue has already been escalated to the mkl team.
Due to many changes, we might not have a solution at this time.
I will consult with the mkl team and will get back to with an estimated timelione.
Best regards,
Khang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Karl,
The latest I received from the mkl team is that the solution might not be available until, to the earliest, the second half of next year.
Best regards,
Khang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Karl.
This issue will be fixed in the upcoming oneAPI 2025.0 release.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page