per-entity - Re: [Per-Entity] implementing a cache on the client
Subject: Per-Entity Metadata Working Group
List archive
- From: David Walker <>
- To: <>
- Subject: Re: [Per-Entity] implementing a cache on the client
- Date: Thu, 4 Aug 2016 13:04:23 -0700
- Authentication-results: spf=none (sender IP is ) ;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
A few comments on this thread:
David On 08/04/2016 07:51 AM, Chris Phillips
wrote:
Yes. We are in general alignment. I won't go as many '>' as you however. I'm reluctant to sacrifice instrumentation at all costs for reliability/performance, but will definitely favour reliability/performance. For the report, I think it's about what's possible and at what estimated cost for an implementation. Do you go to a 'restaurant' for a good meal, a fast meal, or an economical meal? Does one implement MDQ for reliability/performance, with visibility, or cost effectiveness? Either question is a pick 2 from the 3 options unless you aim for 'what's sufficient from each?' C On 2016-08-04, 10:36 AM, "Cantor, Scott" wrote:This is why I'm not so sure of the cost involved in achieving adequate reliability, and adding the requirement to have total visibility on top of that may create a basic conflict. I think reliability/performance >>> visibility. |
Attachment:
signature.asc
Description: OpenPGP digital signature
- Re: [Per-Entity] implementing a cache on the client, Thomas Lenggenhager, 08/04/2016
- RE: [Per-Entity] implementing a cache on the client, Cantor, Scott, 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, Tom Scavo, 08/04/2016
- RE: [Per-Entity] implementing a cache on the client, Cantor, Scott, 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, Walter Forbes Hoehn (wassa), 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, Chris Phillips, 08/04/2016
- RE: [Per-Entity] implementing a cache on the client, Cantor, Scott, 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, Chris Phillips, 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, David Walker, 08/04/2016
- RE: [Per-Entity] implementing a cache on the client, Cantor, Scott, 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, David Walker, 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, Nick Roy, 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, Tom Mitchell, 08/05/2016
- Re: [Per-Entity] implementing a cache on the client, Cantor, Scott, 08/05/2016
- Re: [Per-Entity] implementing a cache on the client, Tom Mitchell, 08/05/2016
- RE: [Per-Entity] implementing a cache on the client, Cantor, Scott, 08/05/2016
- Re: [Per-Entity] implementing a cache on the client, Patrick Radtke, 08/08/2016
- Re: [Per-Entity] implementing a cache on the client, Nick Roy, 08/08/2016
- Re: [Per-Entity] implementing a cache on the client, Patrick Radtke, 08/08/2016
- RE: [Per-Entity] implementing a cache on the client, Cantor, Scott, 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, David Walker, 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, Chris Phillips, 08/04/2016
- RE: [Per-Entity] implementing a cache on the client, Cantor, Scott, 08/04/2016
- Re: [Per-Entity] implementing a cache on the client, Tom Scavo, 08/04/2016
- RE: [Per-Entity] implementing a cache on the client, Cantor, Scott, 08/04/2016
Archive powered by MHonArc 2.6.19.