761
edits
Fr/High-Level Architecture: Difference between revisions
Jump to navigation
Jump to search
Traduction partielle
(Page creation) |
(Traduction partielle) |
||
| Line 19: | Line 19: | ||
{{Multicore}} | {{Multicore}} | ||
'''High-Level Architecture''' ('''HLA''') | '''High-Level Architecture''' ('''HLA''') est une architecture à usage général destinée aux systèmes de simulation informatique distribués. | ||
Rather than have the entire simulation within a single executable, the simulation is split into different [[Federate|Federates]], which interact with each other by a ''Run-Time Infrastructure'' (''RTI'', a message bus that handles serialization of messages, events and objects), with federates typically running in their own threads/processes and each federate process having access to the full virtual process address space provided by the OS instead of having to share it with other subsystems (i.e. 32 bit platforms may make better use of virtual RAM that way). | Au lieu d'avoir toute la simulation dans un seul exécutable (architecture monolithique), la simulation est répartie en différents modules fédérés ([[Federate]]), qui interagissent les uns avec les autres par une infrastructure d'exécution RTI (Run-Time Infrastructure, un bus de messages qui gère la sérialisation des messages, des événements et des objets). Les modules fédérés sont généralement exécutés dans leurs propres [https://fr.wikipedia.org/wiki/Thread_(informatique) threads]/processus et chaque processus fédéré a accès à l'intégralité de l'espace d'adressage du processus virtuel fourni par le système d'exploitation au lieu d'avoir à le partager avec d'autres sous-systèmes (c'est-à-dire que les plates-formes 32 bits peuvent utiliser la RAM virtuelle de maière optimale). | ||
<s>Rather than have the entire simulation within a single executable, the simulation is split into different [[Federate|Federates]], which interact with each other by a ''Run-Time Infrastructure'' (''RTI'', a message bus that handles serialization of messages, events and objects), with federates typically running in their own threads/processes and each federate process having access to the full virtual process address space provided by the OS instead of having to share it with other subsystems (i.e. 32 bit platforms may make better use of virtual RAM that way).</s> | |||
There are three big advantages to this over a monolithic simulation (e.g. FlightGear V3.6): | There are three big advantages to this over a monolithic simulation (e.g. FlightGear V3.6): | ||