All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Connor Doyle <connor.p.d@gmail.com>
Cc: diamon-discuss@lists.linuxfoundation.org
Subject: Re: [diamon-discuss] Interested in integration with cluster management	software
Date: Tue, 22 Sep 2015 20:42:48 +0000 (UTC)	[thread overview]
Message-ID: <378118656.448.1442954568188.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAOB2xgmTY6+4mYVd7gx_CpSoyL5wp6Eca=R4qm-1RsZLunLrFg@mail.gmail.com>

----- On Sep 21, 2015, at 12:09 PM, Connor Doyle connor.p.d@gmail.com wrote:

> Hello,
> 
> I heard about his workgroup through the LF newsletter this morning.
> At Mesosphere we contribute to Apache Mesos, a poular open source
> cluster resource manager and related software.  Much of our work would
> benefit from more standardization (even de-facto standardization)
> around application level tracing and monitoring.  For example, Mesos
> recently added support for modular oversubscription policies for slack
> estimation and QoS control.  We've started discussions about wiring up
> something bespoke for use in Mesos, but standard format for expressing
> SLI/SLO could be better.
> 
> Anyway, just want to express interest in the outcomes, volunteer to
> discuss and help where possible, and say "kudos" for bootstrapping
> this workgroup.

Hi Connor,

Thanks for your interest in the DiaMon Workgroup! Indeed, integrating
tracing/monitoring solutions into a CI resource manager feedback loop
would be an interesting area to tackle. We could then do fine-grained
resource monitoring based on a wide set of metrics, e.g.:

- I/O throughput, max latency,
- Network throughput and max latency,
- CPU utilization,
- Preemption latency,
- Memory usage.

One aspect that pure sampling approaches (profiling) usually don't handle
well are those latency-related. Doing aggregation on tracing data can be
a good way to achieve this. You could then express constraints on the
resources in different ways. Instead of just reserving "capacity", you
could also reserve "latency guarantees".

Thoughts ?

Thanks,

Mathieu


> 
> Best,
> --
> Connor Doyle
> _______________________________________________
> diamon-discuss mailing list
> diamon-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/diamon-discuss

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2015-09-22 20:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 16:09 [diamon-discuss] Interested in integration with cluster management software Connor Doyle
2015-09-22 20:42 ` Mathieu Desnoyers [this message]
2015-10-12 22:10   ` Connor Doyle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=378118656.448.1442954568188.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=connor.p.d@gmail.com \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.