On 20111113@10:55, Carlo de Falco wrote: > $ RSB_USER_SET_MEM_HIERARCHY_INFO="L2:4/64/512K,L1:8/64/32K" octave -q > ... > How can I check whether the system is being actually handled in parallel? > ...
You can influence the OpenMP environment: OMP_NUM_THREADS=1 RSB_USER_SET_MEM_HIERARCHY_INFO="L2:4/64/512K,L1:8/64/32K" octave -q OMP_NUM_THREADS=2 RSB_USER_SET_MEM_HIERARCHY_INFO="L2:4/64/512K,L1:8/64/32K" octave -q ... And also play with librsb's cache parameters: RSB_USER_SET_MEM_HIERARCHY_INFO="L2:4/64/512K,L1:8/64/32K" octave -q RSB_USER_SET_MEM_HIERARCHY_INFO="L2:4/64/2M,L1:8/64/32K" octave -q RSB_USER_SET_MEM_HIERARCHY_INFO="L2:4/64/4M,L1:8/64/32K" octave -q For, only L2 capacity's is influential, but this may change (will change for sure --- I expect a second wave of librsb tuning in the future, as soon as we adapt it to be stable in sparsersb). Declaring a large L2 cache as in: RSB_USER_SET_MEM_HIERARCHY_INFO="L2:4/64/16M,L1:8/64/32K" octave -q may "help" getting a the matrix not subdivided at all, and hence getting no parallelism during multiplication.
pgp8Cunf02JZM.pgp
Description: PGP signature
------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev