forked from bsc-wdc/compss
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathchangelog
351 lines (288 loc) · 17.1 KB
/
changelog
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
COMP Superscalar Framework ChangeLog
Release number: 1.1.1
Release date: 1-Oct-2013
-------------------------------
This is the first public release of the COMP Superscalar Framework.
Release number: 1.1.2
Release date: 5-Jun-2014
-------------------------------
* C/C++ binding.
* Python binding.
* Integrated Development Environment for COMPSs applications (IDE)
* Priority tasks.
* New tracing system using the Extrae tool.
* Deleting a file within an OE removes all the replicas in the system.
* Updated the SSH Trilead adaptor libraries to remove unnecessary sleeps.
* Scripts for submission to queue systems (LSF, PBS, Slurm).
* Configuration of application directory and library path in project XML file.
* Separate logs for resubmitted / rescheduled tasks.
* Create a COMPSs sandbox in the workers instead of JavaGAT's.
Release number: 1.2
Release date: Nov-2014
-------------------------------
* N implementations for task methods, each with its own constraints.
* Constraint-aware resource management.
* Support for multicore tasks.
* Pluggable schedulers: facilitate the addition of new schedulers and policies.
* Extended support for objects in C/C++ binding.
* Extended IDE for N implementations and deployment through PMES.
* Update cloud connector for rOCCI to work with rocci-cli v4.2.5.
* Enhance rOCCI connector to compute the real VM creation times.
* Extended resources schema to support Virtual Appliances pricing.
* New LSF GAT adaptor.
* Deprecated Azure and EMOTIVE Cloud connectors.
* Deprecated Azure GAT adaptor.
Release number: 1.3
Release date: Nov-2015
-------------------------------
New features:
* Runtime:
- Persistent workers: workers can be deployed on computing nodes and persist during all the application lifetime, reducing runtime overhead.
Previous implementation of workers based on a per task process is still supported.
- Enhanced logging system
- Interoperable communication layer: different inter-nodes communication protocol is supported by implementing the Adaptor interface (JavaGAT
and NIO implementations already included)
- Simplified cloud connectors interface
- JClouds connector
* Python:
- Added constraints support
- Enhanced methods support
- Lists accepted as a tasks' parameter type
- Support for user decorators
* Tools:
- New monitoring tool: with new views, as workload and possibility of visualizing information about previous runs
- Enhanced Tracing mechanism
* Simplified execution scripts
* Simplified installation on Supercomputers
Known Limitations:
* Exceptions raised from tasks are not handled by the master
* Java tasks must be declared as public
* Java objects MUST be serializable or, at least, follow the java beans model
* Support limited to SOAP based services
* Persistent Workers do NOT isolate task executions in a sandbox
Release number: 1.4
Release date: April-2016
-------------------------------
New features:
* Runtime:
- Support for Dockers added
- Support for Chameleon added
- Object cache for persistent workers
- Improved error management
- Connector for submitting tasks to MN supercomputer from external COMPSs applications added
- Bug-fixes
* Python:
- Bug-fixes
* Tools:
- Enhanced Tracing mechanism:
· Reduced overhead using native java API
· Support for communications instrumentation added
· Support for PAPI hardware counters added
Known Limitations:
* When executing python applications with constraints in the cloud the initial VMs
must be set to 0
Release number: 2.0 Amapola (Poppy)
Release date: November-2016
-------------------------------
New features:
* Runtime:
- Upgrade to Java 8
- Support to remote input files (input files already at workers)
- Integration with Persistent Objects
- Elasticity with Docker and Mesos
- Multi-processor support (CPUs, GPUs, FPGAs)
- Dynamic constraints with environment variables
- Scheduling taking into account the full tasks graph (not only ready tasks)
- Support for SLURM clusters
- Initial COMPSs/OmpSs integration
- Replicated tasks: Tasks executed in all the workers
- Explicit Barrier
* Python:
- Python user events and HW counters tracing
- Improved PyCOMPSs serialization. Added support for lambda and generator parameters.
* C:
- Constraints support
* Tools:
- Improved current graph visualization on COMPSs Monitor
Improvements:
- Simplified Resource and Project files (NO retrocompatibility)
- Improved binding workers execution (use pipes instead of Java Process Builders)
- Simplifies cluster job scripts and supercomputers configuration
- Several bug fixes
Known Limitations:
* When executing python applications with constraints in the cloud the initial VMs
must be set to 0
Release number: 2.1 Bougainvillea
Release date: June-2017
-------------------------------
New features:
* Runtime:
- New annotations to simplify tasks that call external binaries
- Integration with other programming models (MPI, OmpSs,..)
- Support for Singularity containers in Clusters
- Extension of the scheduling to support multi-node tasks (MPI apps as tasks)
- Support for Grid Engine job scheduler in clusters
- Language flag automatically inferred in runcompss script
- New schedulers based on tasks’ generation order
- Core affinity and over-subscribing thread management in multi-core cluster queue scripts (used with MKL libraries, for example)
* Python:
- @local annotation to support simpler data synchronizations in master (requires to install guppy)
- Support for args and kwargs parameters as task dependencies
- Task versioning support in Python (multiple behaviors of the same task)
- New Python persistent workers that reduce overhead of Python tasks
- Support for task-thread affinity
- Tracing extended to support for Python user events and HW counters (with known issues)
* C:
- Extension of file management API (compss_fopen, compss_ifstream, compss_ofstream, compss_delete_file)
- Support for task-thread affinity
* Tools:
- Visualization of not-running tasks in current graph of the COMPSs Monitor
Improvements:
- Improved PyCOMPSs serialization
- Improvements in cluster job scripts and supercomputers configuration
- Several bug fixes
Known Limitations:
- When executing Python applications with constraints in the cloud the <InitialVMs> property must be set to 0
- Tasks that invoke Numpy and MKL may experience issues if tasks use a different number of MKL threads. 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.
For further information, please refer to “COMPSs User Manual: Application development guide”.
Release number: 2.2 Camellia
Release date: November-2017
-------------------------------
New features:
* Runtime:
- Support Elasticity in SLURM-managed clusters
- Support for Elasticity with Singularity containers
- Integration of Decaf flows as COMPSs tasks
- Changed integratedtoolkit packages by es.bsc.compss (requires changes in Java application codes)
* Python:
- Support for Decaf applications as tasks
- External decorators (MPI, Binary, Decaf, etc.) extended with streams and prefixes support
- Added support for applications that use the argparse library
- Added support for dictionary unrolling on task call
* C:
- Persistent worker in C-binding (enabled with persistent_worker_c=true)
- Inter-task object cache
- Support for object methods as tasks
- Added support applications with threads in master code
Improvements:
- Integration with Jupyter-notebook improved
- Improved cleanup - Unused files removal
- Several bug fixes
Known Limitations:
- Tasks that invoke Numpy and MKL may experience issues if tasks use a different number of MKL threads. 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.
Release number: 2.3 Daisy
Release date: June-2018
-------------------------------
New features:
* Runtime:
- Persistent storage API implementation based on Redis (distributed as default implementation with COMPSs)
- Support for FPGA constraints and reconfiguration scripts
- Support for PBS Job Scheduler and the Archer Supercomputer
* Java:
- New API call to delete objects in order to reduce application memory usage
* Python:
- Support for Python 3
- Support for Python virtual environments (venv)
- Support for running PyCOMPSs as a Python module
- Support for tasks returning multiple elements (returns=#)
- Automatic import of dummy PyCOMPSs API
* C:
- Persistent worker with Memory-to-memory transfers
- Support for arrays (no serialization required)
Improvements:
- Distribution with docker images
- Support for sharing objects in memory between tasks (no file serialization is required now with persistent workers)
- Source Code and example applications distribution on Github
- Automatic inference of task return
- Improved obsolete object cleanup
- Improved tracing support for applications using persistent memory
- Improved finalization process to reduce zombie processes
- Several bug fixes
Known Limitations:
- 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.
Release number: 2.4 Elderflower
Release date: November-2018
-------------------------------
New features:
* Runtime:
- New supercomputers supported Power9 (OpenPower) and ThunderX (ARM 64)
* Python:
- Autoparallel Module to automatically taskify affine loop nests
- Support for Python notebook execution in Supercomputers
- Distributed Data Set library that eases development of PyCOMPSs applications by distributing data, and/or providing most common data operations such as map, filter, reduce, etc.
* C:
- Multi-architecture and Cross-compiling build support
Improvements:
- New example applications distributed on Github
- Reduced overhead of c-binding
- Task sandbox reuse to reduce execution overheads
- Script to clean COMPSs zombie processes
- Several bug fixes
Known Limitations:
- 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.
- 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.
Release number: 2.5 Freesia
Release date: June-2019
-------------------------------
New features:
* Runtime:
- New task property "targetDirection" to indicate direction of the target object in object methods. Substitutes the "isModifier" task property.
- New Concurrent direction type for task parameter.
- Multi-node tasks support for native (Java, Python) tasks. Previously, multi-node tasks were only posible with @mpi or @decaf tasks.
- @Compss decorator for executing compss applications as tasks.
- New runtime api to synchronize files without opening them.
- Customizable task failure management with the "onFailure" task property.
- Enabled master node to execute tasks.
* Python:
- Partial support of numba in tasks.
- Support for collection as task parameter.
- Warnings for deprecated or incorrect task parameters.
- Supported task inheritance.
- New persistent MPI worker mode (alternative to subprocess).
- Support to ARM MAP and DDT tools (with MPI worker mode).
* C:
- Support for task without parameters and applications without src folder.
Improvements:
- Improvements in Jupyter for Supercomputers.
- Upgrade of runcompss_docker script to docker stack interface.
- Several bug fixes.
Known Limitations:
- 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.
- 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.
Release number: 2.6 Gardenia
Release date: November-2019
-------------------------------
New features:
* Runtime:
- New Commutative direction type for task parameter. It indicates that the order of modifications done by tasks of the same type to the parameter does not affect the final result, i.e., tasks operating on a given commutative parameter can be executed in any order between them.
- New "Stream" parameter type, to enable the combination of data-flows and task-based workflows in the same application. The stream parameter type is defined to enable communication of streamed data between tasks.
- Timeout property for tasks. Tasks lasting more than their timeout will be cancelled and considered as failed. This property can be combined with the "onFailure" mechanism.
- Enable the definition of task groups.
- Support for throwing special exceptions (COMPSsExceptions) in tasks and catching them in task groups.
- Task cancellation management in the occurrence of a task group exception and unexpected application finalization (Exception or exit code different from 0)
* Python:
- Enable the declaration of a list of strings as a file collection task parameter.
- Support for Python MPI tasks
* C:
- Support for tasks with fine-grain parallelization with OmpSs-2 programming model.
Improvements:
- New multi-threaded ready scheduler with better scalability.
- Support for task with "isReplicated" properties and parameters with INOUT/OUT direction.
- Optimization in deletion of python objects to avoid large synchronizations in shared file systems.
- Improved the AutoParallel submodule to define data blocks as collection types.
- Several Bug fixes
Known Limitations:
- 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.
- C++ Objects declared as arguments in coarse-grain tasks must be passed as object pointers in order to have 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 underlying 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.
For further information, please refer to “COMPSs User Manual: Application development guide”.
Please find more details about the COMP Superscalar framework at:
http://compss.bsc.es/