Explore the words cloud of the MAESTRO project. It provides you a very rough idea of what is the project "MAESTRO" about.
The following table provides information about the project.
FORSCHUNGSZENTRUM JULICH GMBH
|Coordinator Country||Germany [DE]|
|Total cost||3˙989˙491 €|
|EC max contribution||3˙989˙491 € (100%)|
1. H2020-EU.1.2.2. (FET Proactive)
|Duration (year-month-day)||from 2018-09-01 to 2021-08-31|
Take a look of project's partnership.
|1||FORSCHUNGSZENTRUM JULICH GMBH||DE (JULICH)||coordinator||629˙156.00|
|2||CRAY COMPUTER GMBH||CH (BASEL)||participant||697˙200.00|
|3||EUROPEAN CENTRE FOR MEDIUM-RANGE WEATHER FORECASTS||UK (READING)||participant||655˙375.00|
|4||SEAGATE SYSTEMS UK LIMITED||UK (HAVANT)||participant||595˙280.00|
|5||COMMISSARIAT A L ENERGIE ATOMIQUE ET AUX ENERGIES ALTERNATIVES||FR (PARIS 15)||participant||575˙375.00|
|6||EIDGENOESSISCHE TECHNISCHE HOCHSCHULE ZUERICH||CH (ZUERICH)||participant||567˙955.00|
|7||APPENTRA SOLUTIONS SL||ES (A CORUNA)||participant||269˙150.00|
Maestro will build a data-aware and memory-aware middleware framework that addresses ubiquitous problems of data movement in complex memory hierarchies and at many levels of the HPC software stack.
Though HPC and HPDA applications pose a broad variety of efficiency challenges, it would be fair to say that the performance of both has become dominated by data movement through the memory and storage systems, as opposed to floating point computational capability. Despite this shift, current software technologies remain severely limited in their ability to optimise data movement. The Maestro project addresses what it sees as the two major impediments of modern HPC software:
1. Moving data through memory was not always the bottleneck. The software stack that HPC relies upon was built through decades of a different situation – when the cost of performing floating point operations (FLOPS) was paramount. Several decades of technical evolution built a software stack and programming models highly fit for optimising floating point operations but lacking in basic data handling functionality. We characterise the set of technical issues at missing data-awareness. 2. Software rightfully insulates users from hardware details, especially as we move higher up the software stack. But HPC applications, programming environments and systems software cannot make key data movement decisions without some understanding of the hardware, especially the increasingly complex memory hierarchy. With the exception of runtimes, which treat memory in a domain-specific manner, software typically must make hardware-neutral decisions which can often leave performance on the table . We characterise this issue as missing memory-awareness.
Maestro proposes a middleware framework that enables memory- and data-awareness.
|year||authors and title||journal||last update|
FranÃ§ois Tessier, Maxime Martinasso, Matteo Chesi, Mark Klein, Miguel Gila
Dynamically Provisioning Cray DataWarp Storage
published pages: , ISSN: , DOI:
Are you the coordinator (or a participant) of this project? Plaese send me more information about the "MAESTRO" project.
For instance: the website url (it has not provided by EU-opendata yet), the logo, a more detailed description of the project (in plain text as a rtf file or a word file), some pictures (as picture files, not embedded into any word file), twitter account, linkedin page, etc.
Send me an email (firstname.lastname@example.org) and I put them in your project's page as son as possible.
Thanks. And then put a link of this page into your project's website.
The information about "MAESTRO" are provided by the European Opendata Portal: CORDIS opendata.