Re: FastMove ?


"John O'Harrow" <john@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:48035565$1@xxxxxxxxxxxxxxxxxxxxxxxxx
FastMove should never be slower than using the standard system move. In
fact, the system move routine uses virtually the same code as used by
FastMove (for processors that do not support MMX, SSE etc). It could be
that just adding FastMove to the project causes memory to be allocated
from a different location (not in level 1/2 cache etc), or causes another
routine to be sub-optimally aligned etc.

How much slower is it, and how are you measuring the move performance?

i think it is 2x slower, but I'll check.

It is slower than regular move (d7)...
Any reason for this?





.

Relevant Pages

  • Re: FastMove ?
    ... FastMove should never be slower than using the standard system move. ... a different location, or causes another routine ...
    (borland.public.delphi.language.basm)
  • Re: Textread
    ... Per Isaksson ?:? ... I'm using wintel, ... I would expect sed to work somewhat slower than Jan Simon's ... Jan's routine seems to be based on the same ...
    (comp.soft-sys.matlab)
  • Re: Textread
    ... Per Isaksson  :   0.15625 seconds ... I'm using wintel, ... I would expect sed to work somewhat slower than Jan Simon's ... Jan's routine seems to be based on the same ...
    (comp.soft-sys.matlab)
  • Re: FastCode Poll - Which Functions are Used
    ... Move slower. ... That's why i proposed the FastMove. ... The Fastcode library should simply have all the winner functions and nothing ... Fastmove code isn't efficient moving few amount of bytes ...
    (borland.public.delphi.language.basm)
  • Re: Fearsome Parsing challenge, round 2.
    ... he was saying it ran slower because he *neglected* to ... passing an empty stem to his own routine and a full one to yours. ...
    (comp.lang.rexx)