Mozilla can produce near-native performance on the Web

Re:Mozilla can produce near-native performance on the Web by vilya on Thursday May 23, 2013 @06:10AM (#5756035)

Your comment has made me curious. I tried to think of some examples of performance sensitive apps that aren't amenable to multi-threading and I couldn't, but it seems like they could offer interesting areas for R&D. Can you share some examples?

[ Parent | on HN ]

Re:Mozilla can produce near-native performance on the Web by Yoric on Thursday May 23, 2013 @06:30AM (#5756098)

Consider a single tab of a web browser, for instance. By specification, much of the code must run in the same thread. Keeping the semantics while getting code out of the thread is extremely difficult, often impossible.

I should know, that's my dayjob :)

[ Parent | on HN ]

Re:Mozilla can produce near-native performance on the Web by vilya on Thursday May 23, 2013 @12:17PM (#5757665)

So the reason you can't make it faster than JavaScript by multi-threading it is... because of JavaScript? :-)

I had a look at your profile and it looks like you're doing some very valuable work. I was rather hoping for some examples which didn't involve JavaScript, though.

[ Parent | on HN ]

Re:Mozilla can produce near-native performance on the Web by saucetenuto on Thursday May 23, 2013 @02:14PM (#5758442)

It used to be that almost all PC games were single threaded. Many still are: Civilization 4, Dwarf Fortress, and Morrowind, for example.

[ Parent | on HN ]

Re:Mozilla can produce near-native performance on the Web by fulafel on Friday May 24, 2013 @06:30AM (#5762048)

Many things are hard to parallelize using current technology, and there indeed has been lots of research done on it. History goes back to the supercomputer era (Cray, Connection Machine, Transputer etc.)

The term of art is "inherently sequential" problems (vs "embarrassingly parallel").

In addition, the programming effort gets untenable quickly due to Amdahl's law when the amount of parallelism increases. Eg. if you have 100 cores, even if only 1% of work in your program is sequential, your performance goes down the drain. Currently we're in the comfy phase of the curve with few cores...

We've been making good progress with parallel-minded reimaginings of programming languages and computer architectures on one front: GPUs. On the CPU we are saddled with the inertia and backwards compatibiltiy lock-in of tools and culture (witness lasting use of C++ as a tool to write parallel software)

[ Parent | on HN ]