COMP Superscalar

Improvements:

Known Limitations

• Dynamic constrains are limited to task parameters declared as IN which are not future objects (generated by previous tasks).
• Issues when using tracing with Java 14+. For Java 17+ require to include this jvm flag "-Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true"
• Collections are not supported in http tasks.
• OSX support is limited to Java and Python without CPU affinity (require to execute with --cpu_affinity=disable).  Tracing is not available.
• Reduce operations can consume more disk space than the manually programmed n-ary reduction
• Objects used as task parameters must be serializable.
• Tasks that invoke Numpy and MKL may experience issues if a different MKL threads count is used in different tasks. This is due to the fact that MKL reuses  threads in the different calls and it does not change the number of threads from one call to another. This can be also happen with other libraries implemented with OpenMP.  To fix these issues use the DLB option for in the cpu_affinity flag.
• C++ Objects declared as arguments in a coarse-grain tasks must be passed in the task methods as object pointers in order to have a proper dependency management.
• Master as worker is not working for executions with persistent worker in C++.
• Coherence and concurrent writing in parameters annotated with the "Concurrent" direction must be managed by the underlaying distributed storage system.
• Delete file calls for files used as input can produce a significant synchronization of the main code.
• Defining a parameter as OUT is only allowed for files and collection files.
• There is an issue with hwloc and Docker which could affect to python mpi workers. Fixing it require to upgrade the hwloc version used by the MPI runtime.

For further information please refer to COMPSs Documentation