Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.arch.embedded > #26376

Re: exposing resource usage

From Dimiter_Popoff <dp@tgi-sci.com>
Newsgroups comp.arch.embedded
Subject Re: exposing resource usage
Date 2017-04-14 21:26 +0300
Organization TGI
Message-ID <ocr41u$i1a$1@dont-email.me> (permalink)
References (1 earlier) <qha0fcli6lirq7v2g5eab5agnu0tbq91op@4ax.com> <n5t0fcd1br6t7fnf72gas9edu5oteh45oc@4ax.com> <ocpuv3$5cu$1@dont-email.me> <c251fcdhb8hko59q2dnta5f4eo1h38n39a@4ax.com> <07f1fclgns53g0s3ellasgjs5o0hlcvgvb@4ax.com>

Show all headers | View raw


On 14.4.2017 г. 15:33, upsidedown@downunder.com wrote:
> On Fri, 14 Apr 2017 12:53:54 +0300, upsidedown@downunder.com wrote:
>
>
>> These days the hardware is so cheap that for a RT / high reliability
>> system, I recommend 40-60 % usage of CPU channels and communications
>> links. Going much higher than that, is going to cause problems sooner
>> or later.
>
> I just realized how old I am (still one of the youngest in CAE and
> especially SED newsgroups). During my career in various forms of
> computing, the prace/performance  has been improved by a ratio one to
> a million, depending on how you interpret the Moore's law (is the
> price/performance ratio doubling every 18 or 24 months). With such
> huge rations, it is cost effective to do things in one way and other
> 2-4 years in a completely different way.
>
> Things that required dedicated designs and optimization in the past
> does not make sense these days, unless you are making several million
> copies and want to save a single cent from the production cost.
>
> For low volume products, it doesn't make sense to use too much
> optimization these days. Thus a person with long experience really
> needs to think, how much "clever" features are used.
>
>

The good thing about aging is that we don't notice it a lot ourselves as
long as we are healthy. The outside world takes care of keeping us up
to date of course...

Hardware has always been ahead of software and as hardware becomes
faster for the same tasks done 30+ years ago the gap is allowed to
widen - to scary dimensions I would say. But this is how evolution works
I guess, eventually some balance will be reached. Not that we have
that moment in sight as far as I can see.

Dimiter



Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

exposing resource usage Don Y <blockedofcourse@foo.invalid> - 2017-04-13 18:22 -0700
  Re: exposing resource usage Robert Wessel <robertwessel2@yahoo.com> - 2017-04-13 20:56 -0500
    Re: exposing resource usage Don Y <blockedofcourse@foo.invalid> - 2017-04-13 22:26 -0700
    Re: exposing resource usage upsidedown@downunder.com - 2017-04-14 10:24 +0300
      Re: exposing resource usage Don Y <blockedofcourse@foo.invalid> - 2017-04-14 00:53 -0700
        Re: exposing resource usage upsidedown@downunder.com - 2017-04-14 12:53 +0300
          Re: exposing resource usage upsidedown@downunder.com - 2017-04-14 15:33 +0300
            Re: exposing resource usage Don Y <blockedofcourse@foo.invalid> - 2017-04-14 10:22 -0700
              Re: exposing resource usage upsidedown@downunder.com - 2017-04-17 20:24 +0300
                Re: exposing resource usage Don Y <blockedofcourse@foo.invalid> - 2017-04-17 12:13 -0700
            Re: exposing resource usage Dimiter_Popoff <dp@tgi-sci.com> - 2017-04-14 21:26 +0300
              Re: exposing resource usage Don Y <blockedofcourse@foo.invalid> - 2017-04-14 12:45 -0700
                Re: exposing resource usage Dimiter_Popoff <dp@tgi-sci.com> - 2017-04-15 00:27 +0300
                Re: exposing resource usage Don Y <blockedofcourse@foo.invalid> - 2017-04-14 20:45 -0700
          Re: exposing resource usage Don Y <blockedofcourse@foo.invalid> - 2017-04-14 10:11 -0700
  Re: exposing resource usage Tim Wescott <seemywebsite@myfooter.really> - 2017-04-14 12:54 -0500
    Re: exposing resource usage Don Y <blockedofcourse@foo.invalid> - 2017-04-14 11:44 -0700

csiph-web