Re: Interfaces vs Classes

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Frank Rizzo (none_at_none.com)
Date: 02/24/05


Date: Thu, 24 Feb 2005 14:39:16 -0800

Helge Jensen wrote:
> Frank Rizzo wrote:
>
>> would be huge. That's why I care about speed.
>
>
> Run a test, it is very dangerous to second-guess performance in
> high-level languages. Even more so in runtime-dependant and jit-compiled
> ones.
> Besides, any other processing you do to these object will have to be
> *very* simple indeed for the virtual-dispatch to take up much of the
> processing time.
> Remember, optimization cannot save more cpu-cycles than you spend
> unoptimized, so do your optimization where lots of time is spent.

I agree. This is the place where most of the time would be spent.
Unfortunately, I can't run a test because I don't yet have anything: I
am in the design stage.



Relevant Pages

  • Re: Interfaces vs Classes
    ... high-level languages. ... Even more so in runtime-dependant and jit-compiled ... processing time. ... optimization cannot save more cpu-cycles than you spend ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Cannot optimize 64bit Linux code
    ... of optimization is data dependent. ... I managed to profile the code and ... 78% of the runtime is spent in something called ...
    (comp.lang.c)
  • Re: Speed issue...
    ... 96% of processing time is spent inside TDataConnectThread.Execute ... with WaitForMultipleObjects call. ... But the source for TDataConnectThread is not supplied it seems. ...
    (borland.public.delphi.database.ado)