So they are not exactly/mathematically comparable. The topic is bogus, from the ISA to an application or source code there are many abstraction level and the only metric that we have (execution time, or throughput) depends on many factors that could advantage one or the other: the algorithm choices, the optimization written in source code, the compiler/interpreter implementation/optimizations, the operating system behaviour. This could be legitimate difference, but it's not really related to one architecture being better than the other. ![]() The memory could differ, the core count, etc. When comparing 2 x86 like intel and AMD you should prefer the same binary, unless you also want to allow machine specific optimizations).įinally, the system should also be similar, which is not the case when comparing a smartphone against a pc/macbook. There are of course other factors that must be aligned (and sometimes aren't due to negligence or an intention to cheat) - the workload should be the same (i've seen different versions compared.), the compiler should be as close as possible (although generating arm vs x86 code is already a difference, but the compiler intermediate optimizations should be similar. If you are forced to observe a single point along the graph (which is a legitimate scenario, for example if you're looking for a CPU for a low-power device), at least make sure the comparison is fair and uses the same power envelope. This is usually the case with Arm, as most of these CPUs are tuned for low power, while x86 covers a larger domain and scales much better. One system can win over the low power range, but lose when the available power increases since it doesn't scale that well (or even stops scaling at some point). What you need to look at is the power/performance curve - this graph shows how the system reacts to more power (raising the frequency, enabling more performance features, etc), and how much it contributes to its performance. That ignores the fact that different systems have different optimization points, most often with regards to power (or "TDP"). The common misconception is that you can compare a benchmark across two systems and get a single score for each. The fact that companies publishing (or "leaking") results are biased also doesn't help much. ![]() Of course you can compare, you just need to be very careful, which most people aren't. (Intended this as a comment since this question is off topic, but it got long.). This is technical restrictions, or just marketing? I think that in everyday tasks (Web, Office, Music/Films) ARM (A10X, A11) and x86 (dual core mobile Intel i7) performance are comparable and equal.Īre there any kinds of tasks where ARM really lags far behind x86? If so, what is the reason for this? What's stopping Apple from releasing a laptop on ARM? They already do same thing with migration from POWER to x86. Moreover, if we take the results of Sunspider (JS benchmark), it turns out that Safari on the iPad is gaining more points. And on the iPad Safari works just as well as on the Mac. But it seems to me that this limitation is caused by the format of mobile operating systems (do your work on the go, no mouse, etc), and not by the performance of ARM.Īs an opposite example, let's look at Safari. I agree that the software for the ARM is often only a "lighweight" version of software for desktops. As an example, they lead Photoshop, video conversion, scientific calculations. ![]() They say that x86 is able to perform "more complex tasks". Some people state that these results can not be compared to x86 results. These tests simulate a different load, including the load, which can occur in everyday use. Judging by the latest news, new Apple processor A11 Bionic gains more points than the mobile Intel Core i7 in the Geekbench benchmark.Īs I understand, there are a lot of different tests in this benchmark.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |