Weekly edition	Kernel	Security	Distributions	Contact Us	Search
Archives	Calendar	Subscribe	Write for LWN	LWN.net FAQ	Sponsors

Google's Native Client

Posted Jun 4, 2009 5:50 UTC (Thu) by nikanth (guest, #50093)
Parent article: Google's Native Client

Who needs that extra bit of performance? Even then it can't match native code performance, because of the restrictions implied on the code generated anyway. Java is good enough for me.

A standard to make use of GPU in the webpage is what we need.

(Log in to post comments)

Posted Jun 4, 2009 12:41 UTC (Thu) by nix (subscriber, #2304) [Link]

Those restrictions really don't slow the code down much. They slow down its *theoretical* max speed: a compiler written by an ultraintelligent being could make use of overlapping instructions and that sort of thing.

But code generated by compilers written by human beings never does that. Only attacks do. (And it is very rare to rely on self-modifying code or data execution, either: SELinux and other systems have blocked it for ages, and programs relying on it have long been considered buggy.)

Actually slowdown is noticeable

Posted Jun 4, 2009 19:34 UTC (Thu) by khim (subscriber, #9252) [Link]

You are losing 5-10% of speed with NaCl. But the biggest win is not even speed. It's usage of memory resources. NaCl sandbox is half-meg of memory. Java is few megabytes for "Hello, World". Not even close to being equal.