Even as Android and Windows 8 grow in popularity, Apple's iPad still enjoys a majority of the tablet market. We've found the iPad to be smoother-feeling and more responsive than even the fastest competitors. And we are correct.
One of the first things Intel did was take stock of the tablet space to see how the most popular sellers performed. This had nothing to do with Jobs' Reality Distortion Field; Apple's iPad was truly faster to respond to touch input than the best Android-based models. Windows 7-based tablet's powered by Pine Trail? The worst of the bunch.
To address this challenge, Intel's engineers approached it like NASA and the Apollo program. They couldn’t change their lot by targeting one specific component or element. Instead, they knew they needed to re-think and re-engineer the whole process, optimizing from the moment your finger hits the screen to the moment your task completes.

The first discovery was that Windows 7’s desktop- and workstation-oriented approach to multi-tasking meant that touch input was given the same priority in the execution stack as everything else. On a fast CPU, waiting for the time slice wasn’t a big deal. On a tablet with a low-power processor, this turned into lag and inconsistent responsiveness. Intel says it worked with Microsoft to create a "fast lane" for user input, so that touch would receive the highest priority. This was implemented in Windows 8, and is featured on all tablets and touch-enabled notebooks (including those running Windows RT). Not surprisingly, Windows 8-based machines seem much more responsive than the slates running Windows 7 we reviewed in the past.
Intel then studied the way gestures were recognized and discovered two interesting points. First, electromagnetic interference from the device's LCD was causing noise in most capacitive touch panels, resulting in a lower signal-to-noise ratio. A poor SNR turned into wasted processing cycles to extract legitimate signal from the noise. Working with OEMs, Intel claims it helped improve the analog signaling involved in touch-capable screens.
Though most mainstream folks believe that claims from audiophiles that cable quality is nothing but a voodoo science, techies know that there are times when cabling makes a measurable difference. It was definitely important to SCSI-based storage subsystems. Then, cables became an issue for 80-conductor IDE cables. Even today, a MacBook Pro can crash with a SATA 6Gb/s SSD unless its cable is also wrapped in aluminum foil for shielding. On a tablet, shielding touch sensors from the noisy LCD panel improved the analog signal-to-noise-ratio to such a degree that latency dropped and accuracy improved, yielding faster and more precise input. Acer is one of the first OEMs implementing Intel's technical contribution, and this is little-known feature of the Iconia W510, W710, and Aspire S7. Not all shipping tablets feature this tuning, but an increasing number of OEMs are joining Intel’s performance optimization program. As an analog technology, this can be applied to any touch-capable device. However, Intel is aggressively approaching OEMs manufacturing x86-based tablets and helping them improve this aspect of their technology.
You made a massive assumption here to save yourself a few bucks in shipping costs. Your assumption was wrong, and the delay in processing your RMA is all on you.
Acer manufactures and sells the dock together as a single unit. They separate physically but they are still both part of the same product. It is very reasonable and logical that they would want to examine both together in order to determine the cause of the problem.
It is not reasonable or logical to compare the Acer W510 dock to a keyboard or mouse for a Mac Pro. Keyboards and mice are not system specific and are highly interchangeable. Your Acer tablet may function without the dock, but the dock does not function without the tablet; it's a system dependent peripheral.
Next time you make an assumption that turns out to be wrong, I hope you'll accept some responsibility for it.
As if the whining about having to send the full unit in wasn't bad enough (anyone with any technical knowledge would know to send the complete system, instead of being miserly), but then bad English.
This was a really bad article.
a. this is a good tablet, much better than an ipad
b. it crashes if you try to do things that no ipad could ever do (full pc games)
c. customer service sucks
don't read the article, this has all the info
Chrome currently performs best in Octane. Nearly matched by Firefox. IE10 is nowhere near these two.
Either you took a busted Canary build, or there is something wrong with the test setup.
BTW, why are you testing a Canary build here ? Those are very unstable, and perf goes up and down.
Could you try the latest release Chrome and retest ?
a. this is a good tablet, much better than an ipad
b. it crashes if you try to do things that no ipad could ever do (full pc games)
c. customer service sucks
don't read the article, this has all the info
Plus -------- Acer needs him to pay the shipping charge!!!!!!!!
I have a 9 year old 1.7 GHz Single core Pentium M that can prove the same. Sunspider (0.91) score running Chrome (v24) was 544.6 +/- 6%. 1GB DDR RAM, Windows XP, Intel IGP. Don't remember the clocks.
Sunspider's sensitive to IPC and clock speeds, doesn't seem to care much about core count, as the rest of my little test went like this:
Core i7-3517U @ 2.4 GHz + Turbo = 208
Core 2 Quad Q8400 @ 2.77 GHz = 210.3
Core 2 Duo P8600 @ 2.4 GHz = 262.4
All within a 2% error margin.
Win 8
Win 7 HP
Mac OSX Snow Leopard
All x64.
Intel had sent me a Sony Vaio E14A and an XPS 12. Both touch enabled.
On the Sony, i only used metro to pass time (basically to try it out), otherwise i sat n the desktop...and to be honest, the additional $250 for a touchscreen didn't seem worth it. I did feel like poking at metro, so that's a win, probably, but the entire UI was so cut up...
You constantly had to juggle between both and...every time i'd want to click the start button, i'd freeze, remind myself what was going to happen, and then either avoid clicking or...well, click.
Charms are weird with the mouse. I finally figured why it's called the charms bar: you have to wave your cursor like a wand!
But yeah...it's just too cut up. Same for the XPS 12 in tablet mode. Had to keep going to the desktop for some odd thing, and touch is difficult there. There was also one time when the software keyboard didn't show up, i couldn't understand how to force it, so i had to resort to useing the old on-screen keyboard.
Did you notice how you can't reposition the text cursor by tap-and-holding? You have to use those arrow keys on the keyboard! WP8 is better, thankfully, though that lacks a file system and a decent music app (and a task manager, and a...)...
By biggest complaint with Dell ultrabooks is that they insist on blowing hot air into your lap. Total hybrid-ultrabook killer.
Didn't break 72*C under prime95 (any test) for 10 mins, holding 2.93 to 3 GHz. A core i7-3632QM is mean.
Sad it had Windows 8, touchscreen. It's funny, last year Windows 7 was awesome but OEM bloat and general designs were sub-standard. This year the trend seems to be reversing...
Why can't we edit comments anymore?
And please don't bring the new comments section to these articles!
p.s. Forgot to mention, was a good insight to what's going on behind the scenes at Intel. The only other person except you (Chris) that has writes stuff like this is Anand Shimpi. Real World Tech's David Kanter seems to know a lot about stuff like this too. Of course i'm sure i'm missing a lot of people though!
p.p.s. I wish Intel and AMD would team up to crack mobile. Some sort of agreement that lets them split profits/market share, say 55-45 or something. Not happening, i know
Yeah not the assumption i'd make either (shipping the stuff separately), but you can't really say "who is this guy" on this article.
Unless you're new, in which case you're partially forgiven. Partially.
1. Anything that can be done on a CISC instruction set can be done on a RISC instruction set, it just takes more instructions. Intel's microcode is RISC not CISC. Why? because it's a hell of a lot easier to optimize. It's clear Chris doesn't have a clue as to what this means or why this ties into ARM vs Intel x86
2. Intel didn't optimize their architecture for performance, they just move more of the work onto the CPU
3. Intel worked optimizing schedulers and hardware interfaces for x86, a laudable goal but the same optimizations can easily be applied to ARM
4. Aside from the Windows RT tablet the benchmarks are significantly different systems, not particularly useful
5. The rant is more of a service issue than a hardware issue, important yes but has no bearing on the article other than a broken keyboard
And most importantly
6. The title is misleading, there is no head to head against ARM or Apple. It's optimizations Intel has made to make things work better
Legacy, huh?
Yes, legacy support. Windows 8 programming is meant to be done in Metro, but the desktop supports old software that doesn't work in Metro.
Whether you prefer legacy software or not is up to you, but that doesn't change what it is.