1 / 7

Dynamic Simulation Load Balancing

Dynamic Simulation Load Balancing. A Conceptual Model Eric White, UT-Austin Michael Myjak, UCF/IST. Simulation Resource Consumption. Resource consumption peaks are non-deterministic Performance thresholds exist Computational Network

peri
Télécharger la présentation

Dynamic Simulation Load Balancing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Dynamic Simulation Load Balancing A Conceptual Model Eric White, UT-Austin Michael Myjak, UCF/IST

  2. Simulation Resource Consumption • Resource consumption peaks are non-deterministic • Performance thresholds exist • Computational • Network • Exercise validation dependent upon a minimal, sustained computational capability

  3. Conceputalizing the Problem Space • Load Monitoring • Simulation computation load per host • Network load • Migration • Relocating a runtime object • Migration Policy • Deciding what/when/where to migrate

  4. Load Monitoring • Simulation Hosts • Computational load • Simulation processing • Network interface processing • Monitoring activity, itself • Network Infrastructure • Network gear supporting simulation hosts

  5. Migration • Migrate processes • Binary/Executable format issues in heterogeneous environments • Serialization is a possibility • Migrate Essential State Data (ESD) • Identify the defining attributes per object class • Convert to byte-order-independent formats and transfer

  6. Migration Policy • Requires Load Monitoring data as input • Initiates the when/what/where of migration • Must consider affects of migration over time • I.e., avoid migration “thrashing” • Possibility for multiple migration managers

  7. Potentialities • Add another RTI Service that implements Migration Management • Plug the gap between CMMS and HLA/SOM to identify Essential State Data per object class

More Related