Thanks James! I'd love to talk with you further if you have any interesting or specific problems an algorithm like Relay's might solve.
There are all sorts of possible extension problems I haven't spent time thinking about, such as: - scaling services rather than tasks - more accurately predicting non-linear changes to the metric - using Relay's algorithm as a feedback mechanism to optimize machine learning problems. If you're going to Mesoscon, we could catch up then! Alex On Fri, Jun 5, 2015 at 11:39 AM CCAAT <[email protected]> wrote: > On 06/05/2015 10:09 AM, Alex Gaudio wrote: > > Hi @Ankur, > > > Next, we built Relay <https://github.com/sailthru/relay> and, the Mesos > > extension, Relay.Mesos <https://github.com/sailthru/relay.mesos>, to > > convert our small scripts into long-running instances we could then put > > on Marathon. > >> Thanks. > > > From the first reference page: > " This type of problem is often quite complex, and there is a field > called Control Theory dedicated to problems " > > Oh WOW! Somebody else that understands controls..... > > I was going to suggest some code to build a hybrid Feedback (PID based > on resource utilizations) + Feedforward (based on chronologically > repetitive events) to solve this problem, because it's quite easy to > also integrate relay boards to boot-up/shut-down resources, if systems > are properly configured for such up/down cycling of hardware. There is > also legacy boot/shutdown controls for resources via PXE and such ether > based hardware tricks. > > I think using concepts of process control applied to specific > computational resources, such as ram, cpu, etc etc, also needs to be > addressed with autoscaling. Quick glance at your projects and you > are well underway. > > Hint: You might want to explain some fundamentals of "Control Theory", > as I'm not sure this collective is aware of such simple, beautiful > and robust mathematics. > > > PS: avoid Nyquist stability, for now, but bode plot would be keen! > > > hth, > James > > > >
