4 ms·

Time taken by processing done by the application itself. Faster processing is good even if your backend is mostly waiting for other services - now it can wait f

Time taken by processing done by the application itself. Faster processing is good even if your backend is mostly waiting for other services - now it can wait for more services at the same time and deal with their output faster, allowing your app to use less resources or handle more traffic. That is especially pronounced on scale - if you're spending X million for computing time a month, reducing it by few percent is very interesting to you.

SideburnsOfDoom 5y ago
Both can be relevant. In the real world, designing how to deal with dependencies and data stores is clearly relevant, as it can be the largest large part of the time taken to respond to a given request. It would be a design error to ignore it.
- emteycz 5y ago
  Yes, but external services are irrelevant to performance of . NET.
  - SideburnsOfDoom 5y ago
    If your job is to make performant services, in .NET (or in any similar language) external services are 100% relevant to your job. If You want to be pedantic - and you most certainly do - then only .NET performance itself is relevant to performance of . NET itself, that's a truism, as defined. But this narrow focus is not useful - if you want to do the job, then you have to think a bit more widely, and understand what the real problem is.
    - emteycz 5y ago
      Sorry but this is not pedantic at all. You're saying performance speedup is irrelevant because most time is spent waiting for external services... But that is simply not true if you're beyond just a few servers. Output of external services needs to be processed and having faster software means less resource is spent per request, thus more requests can be served for the same resources. That is very important.
      - SideburnsOfDoom 5y ago
        > You're saying performance speedup is irrelevant I am not saying that; you are oversimplifying into a straw man. great-grand-parent comment is where I literally put a non-zero number to how relevant language perf improvement was: https://news.ycombinator.com/item?id=29295950 https://news.ycombinator.com/item?id=29295950 and later on "Both can be relevant"; which all contradict your characterisation. The only person who said above "it's not relevant" is you, and you also said "external services are irrelevant" - You're projecting the "it's irrelevant" statement onto me here. But the design considerations of how and when to use external services very definitely are relevant to service latency, contrary to what you say, for reasons given multiple times above. Your current odd comments are not fact-based or interesting, so I don't think that you have anything more to add to this discussion at all.

SideburnsOfDoom 5y ago

Both can be relevant. In the real world, designing how to deal with dependencies and data stores is clearly relevant, as it can be the largest large part of the time taken to respond to a given request. It would be a design error to ignore it.

emteycz 5y ago
Yes, but external services are irrelevant to performance of . NET.
- SideburnsOfDoom 5y ago
  If your job is to make performant services, in .NET (or in any similar language) external services are 100% relevant to your job. If You want to be pedantic - and you most certainly do - then only .NET performance itself is relevant to performance of . NET itself, that's a truism, as defined. But this narrow focus is not useful - if you want to do the job, then you have to think a bit more widely, and understand what the real problem is.
  - emteycz 5y ago
    Sorry but this is not pedantic at all. You're saying performance speedup is irrelevant because most time is spent waiting for external services... But that is simply not true if you're beyond just a few servers. Output of external services needs to be processed and having faster software means less resource is spent per request, thus more requests can be served for the same resources. That is very important.
    - SideburnsOfDoom 5y ago
      > You're saying performance speedup is irrelevant I am not saying that; you are oversimplifying into a straw man. great-grand-parent comment is where I literally put a non-zero number to how relevant language perf improvement was: https://news.ycombinator.com/item?id=29295950 https://news.ycombinator.com/item?id=29295950 and later on "Both can be relevant"; which all contradict your characterisation. The only person who said above "it's not relevant" is you, and you also said "external services are irrelevant" - You're projecting the "it's irrelevant" statement onto me here. But the design considerations of how and when to use external services very definitely are relevant to service latency, contrary to what you say, for reasons given multiple times above. Your current odd comments are not fact-based or interesting, so I don't think that you have anything more to add to this discussion at all.