Skip to content

BodhviGaur/Cloud-Flow-Size-Prediction

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

52 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Cloud-Flow-Size-Prediction

Paper Followed: Is advance knowledge of flow sizes a plausible assumption?https://www.usenix.org/conference/nsdi19/presentation/dukic

Note: To compare the effect of knowing flow sizes on the scheduling algorithms, we have to organise the way tasks reach the scheduler. This must be the same for us to test/compare how the scheduling algorithms are affected. We do this in the following manner: We will generate a list of many small tasks for testing by randomly running 1 of 3 algorithms (KMeans, SGD, Pagerank), and allocate a starting time to each randomly between (0 and 1,00,000).

We have created a miniature dataset to allow testing (we have a flow in the actual test set amounting to a whooping 93 hrs. We assume no one will run our test that long).

This consists of 10 jobs from KMeans, SGD and Pagerank.

SJF ideal* : 4762.1541028.
FIFO ideal* : 5765.56560111.

Aging (500ms) : 4564.5097878.
Aging (50ms) : 5082.73901892.
SJF Predicted with Neural Network : 4672.01515794.

Runtimes NN PageRank: 1551 seconds (25 min)
NN KMeans: 460.17 seconds (7.6 min) NN SGD: 5798.993380 seconds (1.6 hours)

  • where ideal means that the scheduling algorithm used actual flow runtimes. All other algorithms were tested on predicted run times.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published