Struct ComponentsPattern

pub struct ComponentsPattern { /* private fields */ }

Divide the topology according to some given link classes, considering the graph components if the other links were removed. Then apply the global_pattern among the components and select randomly inside the destination component. Note that this uses the topology and will cause problems if used as a sub-pattern.

Trait Implementations

impl Debug for ComponentsPattern

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Pattern for ComponentsPattern

fn initialize( &mut self, _source_size: usize, _target_size: usize, topology: &dyn Topology, rng: &mut StdRng, )

Fix the input and output size, providing the topology and random number generator. Careful with using topology in sub-patterns. For example, it may be misleading to use the dragonfly topology when building a pattern among groups or a pattern among the routers of a single group. Even just a pattern of routers instead of a pattern of servers can lead to mistakes. Read the documentation of the traffic or meta-pattern using the pattern to know what its their input and output.

fn get_destination( &self, origin: usize, topology: &dyn Topology, rng: &mut StdRng, ) -> usize

Obtain a destination of a source. This will be called repeatedly as the traffic requires destination for its messages.

impl Quantifiable for ComponentsPattern

fn total_memory(&self) -> usize

Get the total memory currently being employed by the implementing type. Both stack and heap.

fn print_memory_breakdown(&self)

Prints by stdout how much memory is used per component.

fn forecast_total_memory(&self) -> usize

Get an estimation on how much memory the type could reach during the simulation.