Formular una preguntaFormular una pregunta
 

RespondidaOverhead with using CCS scheduler using MPI

  • lunes, 08 de diciembre de 2008 23:37jingsongw Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    I'm setting up a compute cluster that uses MPI to generate calculations on the fly in short amounts of time <3s. I was wondering what kind of overhead times I would possibly see if I submitted jobs using the CCP API, or should I just use the Cluster.ExecuteCommand method instead?

    If neither of these is a possibility because the overhead of the CCP framework is too large, is there a way to bypass that and still harness the power of the MPI.NET?

Respuestas

  • jueves, 25 de junio de 2009 1:56Don PatteeMSFT, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respondida
    You may want to look at the 'parametric sweep' and 'SOA'/'WCF' features in the HPC documentation. Those both enable more calculations to be done without paying a full job submission penalty for each one.

Todas las respuestas

  • jueves, 25 de junio de 2009 1:56Don PatteeMSFT, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respondida
    You may want to look at the 'parametric sweep' and 'SOA'/'WCF' features in the HPC documentation. Those both enable more calculations to be done without paying a full job submission penalty for each one.