SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Advanced Micro Devices - Moderated (AMD) -- Ignore unavailable to you. Want to Upgrade?


To: pgerassi who wrote (264315)8/11/2010 4:27:41 PM
From: fastpathguruRead Replies (1) | Respond to of 275872
 
X11R6 X-Server on Linux with 256MB DDR2 memory and 1GHz ARM Cortex A9MP/DC. And anything with a 3-5 second response time for user input is atrocious. Sub 1 second is the typical required response time which all tested x86 systems had no trouble beating even ancient ones.

Silly question, but the network is identical too?

Sounds very... odd, seeing as how an X session displaying a remotely hosted X app doesn't really do anything but relay input to the app, and process primitive rendering requests. Lag between sending a mouseclick event and updating a fraction of a 640x480 display is not going to be that CPU's fault.

The latest gen ARM smartphones can do QuakeIII timedemos without breaking a sweat...

See Samsung Galaxy S (Samsung Hummingbird w/1xARM Cortex A8):

androidspin.com

The next next-gen phones will have dual-core ARM A9, even more powerful 3d/vid-codec, etc. etc... I just don't see them lacking performance at all in the role of convenient-always-at-my-side-MID.

fpg



To: pgerassi who wrote (264315)8/11/2010 5:59:29 PM
From: neolibRead Replies (1) | Respond to of 275872
 
And anything with a 3-5 second response time for user input is atrocious.

So what the hell is it doing at 1Ghz DC for 3-5 seconds? Something does not add up here.