Re: [ Firefox 3.6.4 ] Poor performance in path tracing example (using WebWorkers)

On 5/25/2010 4:25 AM, Kr@n wrote:
>
> Hi,
>
> I recently came across an implementation of path tracing in
> javascript, using web workers. Since the developer himself said
> performance was noticeably better in Chrome, I tried FF3.6.4 beta and
> Chrome 4.1.249.1064 (45376) and Chrome is at least 10 times faster (on
> an Intel E8500 CPU, 2GB RAM, but I don't think this is relevant) ...
>
> It may be caused by poor tracing in FF (JaegerMonkey would thus kick
> in and close the gap), but in case it's not, here is the URL :
> http://29a.ch/sandbox/2010/cornellbox/

I think it's not tracing:

Recording starting from 
http://29a.ch/sandbox/2010/cornellbox/worker.js:194@100
(FragID=000000)
Abort recording of tree 
http://29a.ch/sandbox/2010/cornellbox/worker.js:194@100
at http://29a.ch/sandbox/2010/cornellbox/worker.js:201@0: Inner tree is 
an unsupported type of recursion.

Could you try recoding it to use iteration instead of recursion in 
Renderer.trace and see what that does to perf?

Dave