planning of experiments #31

New issue

Closed

opened 2020-06-03 00:09:43 +02:00 by schmittlauch · 0 comments

schmittlauch commented

2020-06-03 00:09:43 +02:00

Owner

What metrics to measure?

only measure relay node performance/ load, ignore storage node load in the scope of this project
key metric: number of posts to be relayed by node per time = |subscribers| * |incoming posts|
resolution of 1 day might be good enough
effectivity of load balancing:
- distribution of load among homogenous nodes
- match of load to load target for inhomogenous nodes

How to measure them?

relay nodes report numer of relayed posts per time slice

Parameters to examine

number of hashtags
- k-choices doesn't protect against overload at a single hashtag
assumed distribution of subscribers
- assume power law distribution of users over instance https://dl.acm.org/doi/pdf/10.1145/3355369.3355572
- assume that each poster also makes their instance subscribe to that tag
- but multiple subscriberst can be on the same instance => only one subscription for all tof them
node resources: homogenous or non-homogenous
- start with homogenous nodes fo non-kchoices simulation
node IPs and domains => node IDs
- can be taken from instances.social data set (Großer Beleg)

scenarios to simulate

## What metrics to measure? - only measure relay node performance/ load, ignore storage node load in the scope of this project - key metric: **number of posts to be relayed by node per time** = |subscribers| * |incoming posts| - resolution of 1 day might be good enough - effectivity of load balancing: - distribution of load among homogenous nodes - match of load to load target for inhomogenous nodes ## How to measure them? - relay nodes report numer of relayed posts per time slice ## Parameters to examine - number of hashtags - *k-choices* doesn't protect against overload at a single hashtag - assumed distribution of subscribers - assume power law distribution of users over instance https://dl.acm.org/doi/pdf/10.1145/3355369.3355572 - assume that each poster also makes their instance subscribe to that tag - but multiple subscriberst can be on the same instance => only one subscription for all tof them - node resources: homogenous or non-homogenous - start with homogenous nodes fo non-kchoices simulation - node IPs and domains => node IDs - can be taken from *instances.social* data set (Großer Beleg) ## scenarios to simulate