ai-se / RIOT

IEEE Cloud18: RIOT: a Novel Stochastic Method for Rapidly Configuring Cloud-Based Workflows
MIT License
1 stars 0 forks source link

Experiment 5: SWAY vs. MOEA #10

Closed ginfung closed 7 years ago

ginfung commented 7 years ago

Colored cell = not good in sway Runtime runtime

Hypervolume hv

Spread spread

IGD igd

ginfung commented 7 years ago

combine

timm commented 7 years ago

so from the above, i see that

1) SWAY is VASTLY faster than the rest 2) in the majority case, it is as good as the best (and when it fails, it fails close to the best)

how you do it? any new feature engineering? any new diversity oeprators?

ginfung commented 7 years ago

image

timm commented 7 years ago

not seeing the intuition prior SWAY-based work was insufficient for crowd configuration because X hence we tried Y,Z

ginfung commented 7 years ago

notice that we can treat SWAY as a simplified version of PCA -- each time we get principal Components->map candidates to PC-> delete half of them

SWAY fails since 1) even though sort candidates with the key PC, we can't say first, or second, half of them are unpromising. Especially in the multi-objective problem. sometimes, first half perform well in objective A, and second half perform well in objective B 2) most of the time, extreme points cannot dominate each other. making algorithm O(N), not O(lg N)

what should we do? 1) similar configuration indicates similar objective; i.e. I can ask my neighbor if I want to evaluate myself ( think about K-means)

2) model is a black box. BUT we know its monotonicity. (increase CPU/memory - > reduce time. increase $$) there for, to estimate one objective, we can add delta to neighbor's obj.

to get delta, see image

I tried to explain these in section 4.3

ginfung commented 7 years ago

unlike sway which is recursively pruning, now we get all objective estimations first, then non-dominate sorting.