Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

- Intel Community
- Software
- Software Development SDKs and Libraries
- Intel® oneAPI Math Kernel Library
- The difference in the common sparse solver function result and cluster sparse solver function result

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page

Anonymous100

Beginner

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

11-30-2015
02:08 AM

22 Views

The difference in the common sparse solver function result and cluster sparse solver function result

Hello.

I'm Using MKL Pardiso Sparse Solver (PARDISO).

Some time ago, I Using Intel Parallel Studio 2013 Version (MKL 11.2).

Recently, I'm Update Intel Parallel Studio 2016 (MKL 11.3).

This Version Support Cluster Sparse Solver. so I using this Function.

But Solving result is difference. (about 0.02)

Originally does the other result come out?

Or is there the condition getting the little more exact result?

Link Copied

1 Reply

Zhang_Z_Intel

Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

11-30-2015
12:46 PM

22 Views

You may attach your matrix and your code here, so we can understand the situation better.

When you go from PARDISO to the cluster sparse solver, the level of parallelism may have changed. You were using multiple threads before and are now using multiple MPI processes with, potentially, multiple threads in each process. Can you describe the configuration of your cluster? What kind of CPUs? How many nodes and MPI processes? How many threads do you use for each process, etc.?

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page

For more complete information about compiler optimizations, see our Optimization Notice.