This repository has been archived on 2024-04-10. You can view files and clone it, but you cannot make any changes to it's state, such as pushing and creating new issues, pull requests or comments.

Pradyumna Kaushik 25bf363d2c Merged in tasksToScheduleWindow (pull request #5) ... TasksToScheduleWindow Approved-by: Akash Kothawale <akothaw1@binghamton.edu>		2018-09-23 19:01:17 -04:00
..
base.go	Merged in akash/LogPolicySwitch (pull request #4)	2018-09-23 18:57:24 -04:00
bin-packing.go	Merged in tasksToScheduleWindow (pull request #5)	2018-09-23 19:01:17 -04:00
electronScheduler.go	Merged in akash/LogPolicySwitch (pull request #4)	2018-09-23 18:57:24 -04:00
first-fit.go	Merged in tasksToScheduleWindow (pull request #5)	2018-09-23 19:01:17 -04:00
helpers.go	ignored error returned from LaunchTasks. Technically, this error shouldn't occur. Retrofitted scheduling policies to not receive an error when calling LaunchTasks(...)	2018-09-23 18:30:12 -04:00
MaxGreedyMins.go	Merged in tasksToScheduleWindow (pull request #5)	2018-09-23 19:01:17 -04:00
MaxMin.go	Merged in tasksToScheduleWindow (pull request #5)	2018-09-23 19:01:17 -04:00
schedPolicy.go	added a baseSchedPolicyState struct in schedulers/schedPolicy.go. This struct would store information common to scheduling policies. Added member called numTasksScheduled to baseSchedPolicyState that would keep count of the number of tasks that the current scheduling policy has scheduled. Moved the logic to switch (currently performing a random switch) to baseSchedPolicyState#switchIfNecessary(...) and retrofitted all scheduling policies to call this instead of inlining the code in each of them.	2018-09-23 18:28:11 -04:00
states.go	Fix: mesos-go imports	2018-09-23 17:31:03 -04:00
store.go	added utility to compute the scheduling window. Right now there's only criteria on which this is determined -- fillNextOfferCycle. So, the schedWindow is the max number of tasks, that aren't yet scheduled, whose aggregate resource requirement is as close as possible to the resource available in the next round of resource offers. To be able to make the most use of the next offer cycle, one would need to perform a non-polynomial search of the TaskQueue and as this is computationally expensive, a linear search is performed on the TaskQueue. Retrofitted scheduling policies to also call utilities.schedUtils#schedWindowResizingStrategy#Apply before switching to a new scheduling policy.	2018-09-23 18:03:14 -04:00