2 ms·
The x86 comfort zone is always by your side. With virtualization (and app virtualization) you can run x86 apps seamlessly. Fortunately Office apps aren't CPU
by kenjackson 16y ago
The x86 comfort zone is always by your side. With virtualization (and app virtualization) you can run x86 apps seamlessly. Fortunately Office apps aren't CPU bound.
Right, this has always been the play on virtualization for the OS. Don't get stuck in legacy mode, virtualize, and move on. MS may finally be doing what everyone said they should do.
- wmf 16y agoWith virtualization (and app virtualization) you can run x86 apps seamlessly. Not on ARM. Emulation is possible but will be really slow.
- kenjackson 16y agoHow slow? I did some quick profiling of Word and Excel doing basic stuff (text entries, making charts, but no hardcore calculations). Avg CPU utilization: 1%. Peak CPU utilization: 4%. A factor of 10x slowdown would probably be reasonable. Is the current state of the art on ARM able to get it below 10x?
- rbanffy 16y agoAverage CPU utilization is misleading. Just wait to see how long those small brief moments when you have 50% CPU utilization will extend into minutes under emulation. And, BTW, nobody would buy a computer that can run only Windows and Office. To be fair, only the Office part would have to run under emulation. As soon as the code calls into core Windows, the machine would be running ARM code. I don't know where the boundary is with Office.
- kenjackson 16y agoThat's why I also noted the peak CPU utilization (4%). I do agree that only running Windows and Office is not sufficient. But its a starting point for the discussion.
- rbanffy 16y agoI would have to measure it again, but I remember seeing numbers much higher than 4% peak when I had to use Office. It could be some other latency disguising as CPU usage. The fact is it's been a while since I last used Windows and Office 2010 and I would prefer it to remain that way. Also, consider that A-15 may be competitive with current x86 designs. Who knows what will Intel and AMD bring by the time A-15/Denver machines hits the shelves. That said, I find my modest Atom good enough for Django programming the slightly less modest Core i5 very reasonable with Java and Eclipse. It will take some iterations until ARM catches up (I assume it will move faster than x86 because of its simple architecture). I have no doubt a relatively modest ARM machine will be good enough for most of my then current usage.
- jawee 16y agoHave you ever tried running Office with a little network latency? The 10x slowdown is barely usable and unavoidably annoying, especially if you're used to a faster computer.
- kenjackson 16y agoProbably 50% of the time I use office it is over remote desktop over VPN, and honestly I don't really notice it (I really don't notice it for any application except streaming media over RDP isn't great, but surprisingly acceptable). Maybe we just have really fast networks.
- rbanffy 16y agoWith Remote Desktop you are running Office on the machine that has a fast network and only transferring the pixels that change. That's not, probably, what jawee was saying.
- kenjackson 16y agoBut I use Office completely w/o a network connection quite often. It's not a web app. It rarely touches the network. Just about the only time I hit the network is when using Excel to access a relational store or if your document is on a file share (and even then the document is stored locally after opening it). I assumed he meant something where the network latency would impose a keystroke-level degredation in performance.
- rbanffy 16y agoI think jawee's point is that little latencies (memory, cache, IO) quickly add up to make emulation much harder than that. The picture may not be that grim if at least timing-critical parts of Office can be made into fat binaries. I would not bet on straight emulation of uncooperative code, however.
- deleted 16y ago[deleted]