Description:
While running DataSpaces/DIMES with MPI+OpenMP multi-threads code (#OMP > 1), the main loop will get impacted and delayed even without calling any DataSpaces/DIMES put/get.
One single thread in master peer/process gets delayed, the rests are normal. Because of the sync, the entire execution delays as well.
Quick solution:
Initiate OpenMP, e.g., omp_init() before initiating DataSpaces/DIMES. The order is omp_init()->dspaces_init() ...
Cause:
May be resource conflicts. Current debugging situation: dc_base_gni.c is the layer causing it. If we only start rpc_server and dataspaces_server without registration on dc_base level, there is no delay any more.
Description: While running DataSpaces/DIMES with MPI+OpenMP multi-threads code (#OMP > 1), the main loop will get impacted and delayed even without calling any DataSpaces/DIMES put/get.
One single thread in master peer/process gets delayed, the rests are normal. Because of the sync, the entire execution delays as well.
Quick solution: Initiate OpenMP, e.g., omp_init() before initiating DataSpaces/DIMES. The order is omp_init()->dspaces_init() ...
Cause: May be resource conflicts. Current debugging situation: dc_base_gni.c is the layer causing it. If we only start rpc_server and dataspaces_server without registration on dc_base level, there is no delay any more.