Tasks and Status for the simulation of the LAr slice

Based on this meeting: https://twiki.cern.ch/twiki/bin/view/Main/AdvancesWainer%2cEukeni%2cMati%2cAndy


  1. [DONE] Host multi-puerto [generator]: los felix van a tener al menos 2 puertos de salida (uno a cada switch). Ahora el template del pdm solo permite 0 o 1 puerto.
  2. [DONE] multi-path + bonded links [generator+simulation]: los datos de un felix hacia un swrod puede tomar 2 posibles caminos (uno por cada switch). Ademas, Los 2 links que salen del felix en la realidad son bonded-links (la aplicación lo ve como uno solo).
    Details: Routing for multi-path flows
  3. [DONE] Host multi-flow [simulation]: los felix van a generar datos y otros flujos (ej: monitoring). Ahora la simulacion permite un unico flow por generador. (esto por ahora no es tan prioritario, porque vamos a arrancar unicamente con datos).
    Details: Link al google doc de andy
  4. Validation: Eukeni nos paso codigo=> hay que revisarlo/rehacerlo
  5. Traffic characterization:
    1. To characterize the felix traffic patter we will follow up with Jorn.
      [DONE]. See meeting Caracterizando la generacion de trafico de los servidores felix (Jorn, Matias, Andy)
    2. [DONE] Implement felix traffic into the simulation
      Details: https://twiki.cern.ch/twiki/bin/view/Main/PhaseISimulation_FelixDistribution
    3. [DONE] The monitoring traffic will be a percentage of the data traffic.
    4. Still need to understad DCS traffic.
  6. simulation scenarios: it is interesting to use the simulation in the following scenarios (with this priority):

    1. [DONE] Base case: felix servers and swrod only with 1:1 data flow communication. There should be no bottleneck or queueing. Boring case.
      See details here: Simulation Results for the Basic Scenario
    2. *[DONE] Realistic Felix traffic pattern:*
      details: realistic felix traffic pattern
    3. [DONE] Add Monitoring traffic: add the monitoring traffic on top of the data. see traffic characterization below. ¿how does it affect data traffic?¿how to setup queue priorities? estimatemax % of monitoring traffic according to link BW.
      details: Monitoring Traffic flows to HLT mon-servers and Finding monitoring congestion point
    4. Add DCS traffic: add the DCS traffic, which is required to have a minimum latency. ¿how to setup queue priorities to minimize lantency? Estimate expected DCS latency.

  1. [WIP] TDR document: it would be good to include a SMALL, CONCISE paragraph of the simulation tools that support the PhaseI design decisions. Deadline: end-of-year. Follow-up discussion with Eukeni and Rodrigo.
    We will provide a first draft after the 7th of Dic when Rodrigo finishes the CIMS3 congress organization.
  2. [WIP] Reports: morefrequent written reports and meeting would be appreciated. It was agreed to prepare a report at least once a month.
-- MatiasAlejandroBonaventura - 2016-12-07
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2016-12-13 - MatiasAlejandroBonaventura
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback