Three.js performance is highly dependent on how the browser interacts with 
available graphics hardware. Chrome is the browser of choice for Three.js 
developers, but Firefox has made great improvements in the last couple 
years. If you're using the latest version of Firefox, then the bottleneck 
will be the GPU on your machine: if the browser can't interact efficiently 
with the GPU then the CPU has to pick up the slack.

Rendering this scene in Firefox on my year-old Macbook Pro settles down to 
around 30% of total CPU load. By contrast, rendering this scene in Firefox 
on my slightly older Windows 10 machine with a better GPU settles down to 
about 2% of total CPU load.

Opening multiple browser windows with Three.js scenes on my Macbook will 
bring the machine to a crawl and this is simply a machine limitation. I was 
initially worried this would be a major problem for Sage notebooks but it 
turns out not to be, since the notebook is a single browser window.

On Friday, December 2, 2016 at 7:31:27 AM UTC-8, tdumont wrote:
>
> I have just tried three.js in 7.5 beta 5, doing (as in the doc): 
>
> sage: sage: p1 = sphere(color='red', opacity='.5') 
> ....: sage: p2 = sphere((-1,-1,1), color='cyan', opacity='.3') 
> ....: sage: p3 = sphere((1,-1,-1), color='yellow', opacity='.7') 
> ....: sage: show(p1 + p2 + p3, viewer='threejs') 
>
> My firefox is launched, and the result is nice ! 
>
> But looking at the cpu consumption of firefox, I found that it takes 
> between 60% and 89% of one processor cpu time, even when I look at the 
> steady graphic (mouse pointer out of the window). 
>
> May be there is nothing to do (some loop...),  but this is quite much! 
>
> t.d. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to