This is a continuation of my old question "Does PARDISO have core access limit" with new information. I'll put a quick summary and the new question:
I run a code on Windows based HP DL980 server with 80 cores and 1TB RAM. Originally the OS is Windows Server 2008 SP2 (Which, I was informed, is based on Windows Vista). It seemed work properly. The IS&T upgraded the OS to Windows Server 2008 R2 SP1 (Based on Windows 7). However, the code now can only access to a small portion of the cores (25%), the rest of the cores are set idle.
I posted my problem here and got help on how to manually set up the MKL access to the cores. After many rounds of trial and error on the machine, we finally were able to run on up to 50% of cores, even for multiple users. But there are still half of the cores set idle.
In one of HP's online documents it is stated: "The processor group concept was introduced in Windows 7 and Windows Server 2008 R2 to support more than 64 logical processors. Any machine with more than 64 logical processors has more than one processor group by necessity. Drivers and applications are all expected to run properly in the multi-group context if coded properly. "
My question is: Are MKL routines, in particular PARDISO, aware of this "multi-group context" and can work properly with multiple processor groups, each with up to 64 cores? If yes, since which version? (I may need an upgrade then).