Endianness conversion cost on architectures -


today there 2 kinds of cpu architectrues, big endian , little endian. data needs converted between 2 representations. each cpu architecture, instruction set in particular, different , each allows different implementations changing endianness. cpus contain specific instructions while others not.

my question this, today's architectures more efficient have data , convert on le architectures or other way around, in order minimize data conversion latency , maximize throughput in le communication.

second question, can cost of conversion quantified, there data on matter?

how costly conversion in java byte array? there data on specific jvms on specific architectures? different on dalvik?

afaik relevant architectures x64, arm, mips , jvm/dalvik. missing any?

data should in native endian except case copy value , send without processing. how can operations reversed endian (except bitwise operators)? network activities slower cpu, not compared ram. you'll hardly ever see difference in speed memory bound.

storing data basic of computers, why few architectures relevant? architectures must follow specific endianness (such x86/x86_64) or bi-endian (arm, mips...)


Comments

Popular posts from this blog

html - Sizing a high-res image (~8MB) to display entirely in a small div (circular, diameter 100px) -

java - IntelliJ - No such instance method -

identifier - Is it possible for an html5 document to have two ids? -