I’m not finding what I was remembering, but did find these two settings:
CHPL_RT_OVERSUBSCRIBED=yes CHPL_RT_NUM_THREADS_PER_LOCALE=8 # or whatever
That said, I’m not confident that this is sufficient. Specifically, I don’t recall that anything will make sure that the two processes won’t use the same cores for each of their 8 threads (?). Elliot’s definitely the expert here, so I’d suggest checking with him next week (though actually he may still be online now… even though it’s late on a Friday on the east coast. Of course, this is true for you as well… :) )
Now the arkouda-njit directory is organized as follows.
client : all python code
arkouda_graph : graph extension
suffix_array: suffix array extension
benchmarks: python code to check different extension functions.
server : modules of different chapel code
UniTestCh: chapel unit test code. we have not implemented this part.
After compiling the server binary using Kyle's python script, we take the following steps to call the extended functions.
(1) under the master arkouda directory, copy the arkouda-njit directory to here and rename it as arkouda_njit or
create a arkouda_njit link to the arkouda-njit directory
(2) under benchmarks, for different python code, import arkouda_njit as njit
(3) call all the extended function as njit.function
This method can maintain the extended code independently, at the same time, use the extended functions just like before under the master directory.
We have done some preliminary tests and it can work.
If you have any suggestions, please let me know.
Michael Merrill is inviting you to a scheduled Zoom meeting.
Topic: Arkouda Weekly Zoom Meeting Time: recurring meeting Tuesdays @ 1pm ET
Meeting ID: 777 1700 0423 Passcode: kjM3WS