Flow scheduling is now updated directly in Topology::updateCapacity() to ensure correctness of the binomial_heap at all times
Vertex now has an additional uint asid field to support locality info
Flow scheduling is now updated directly in Topology::updateCapacity() to ensure correctness of the binomial_heap at all times
Vertex now has an additional uint asid field to support locality 
For each AS, a cache element has to be specified in the topology file
Flow scheduling is now updated directly in Topology::updateCapacity() to ensure correctness of the binomial_heap at all times
Vertex now has an additional uint asid field to support locality; for each AS, a cache element has to be specified in the topology file
Changed the topology to a directed graph to support asymmetric links and handle uplink/downlink capacity separately
Implemented stats collection in the topology (avgFlowDuration, avgLoad per edge, locality%)
Flow scheduling is now updated directly in Topology::updateCapacity() to ensure correctness of the binomial_heap at all times
Vertex now has an additional uint asid field to support locality; for each AS, a cache element has to be specified in the topology file
Changed the topology to a directed graph to support asymmetric links and handle uplink/downlink capacity separately
Implemented stats collection in the topology (avgFlowDuration, avgLoad per edge, locality%)
Starting implementation of testRun, content generation, views generation etc
Scheduler now requires roundDuration at construction, advanceClock() returns false when the simTime reaches that value
Content should correctly move between beforePeak, atPeak and afterPeak lists in TestRun
None of this has been tested yet!
Scheduler now requires roundDuration at construction, advanceClock() returns false when the simTime reaches that value
Content should correctly move between beforePeak, atPeak and afterPeak lists in TestRun
None of this has been tested yet!
Scheduler now requires roundDuration at construction, advanceClock() returns false when the simTime reaches that value
Content should correctly move between beforePeak, atPeak and afterPeak lists in TestRun
Implemented scheduling of requests according to a discrete probability over the week to account for peak times
None of this has been tested yet!
Scheduler now requires roundDuration at construction, advanceClock() returns false when the simTime reaches that value
Content should correctly move between beforePeak, atPeak and afterPeak lists in TestRun
Implemented scheduling of requests according to a discrete probability over the week to account for peak times
None of this has been tested yet, but then again I need a bigger topology with enough ponNodes to act as requesters (I have no control on the amount of requests I get as it's dictated by the distribution parameters taken from the popularity evolution paper)
Scheduler now requires roundDuration at construction, advanceClock() returns false when the simTime reaches that value
Content should correctly move between beforePeak, atPeak and afterPeak lists in TestRun
Implemented scheduling of requests according to a discrete probability over the week to account for peak times
None of this has been tested yet, but then again I need a bigger topology with enough ponNodes to act as requesters (I have no control on the amount of requests I get as it's dictated by the distribution parameters taken from the popularity evolution paper)