Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

2016-12-04 Thread William Stein
On Sun, Dec 4, 2016 at 10:37 AM, Dima Pasechnik wrote: > > > On Saturday, December 3, 2016 at 10:34:50 PM UTC, Paul Masson wrote: >> >> >> >> On Saturday, December 3, 2016 at 2:30:36 PM UTC-8, William wrote: >>> >>> On Sat, Dec 3, 2016 at 2:28 PM, Paul Masson

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

2016-12-04 Thread Dima Pasechnik
On Saturday, December 3, 2016 at 10:34:50 PM UTC, Paul Masson wrote: > > > > On Saturday, December 3, 2016 at 2:30:36 PM UTC-8, William wrote: >> >> On Sat, Dec 3, 2016 at 2:28 PM, Paul Masson >> wrote: >> > There's apparently no good way in general to test whether the

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

2016-12-03 Thread Paul Masson
On Saturday, December 3, 2016 at 2:30:36 PM UTC-8, William wrote: > > On Sat, Dec 3, 2016 at 2:28 PM, Paul Masson > wrote: > > There's apparently no good way in general to test whether the scene is > > unchanged. This is a known issue: > > > >

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

2016-12-03 Thread William Stein
On Sat, Dec 3, 2016 at 2:28 PM, Paul Masson wrote: > There's apparently no good way in general to test whether the scene is > unchanged. This is a known issue: > > https://github.com/mrdoob/three.js/issues/7670 > > One of the comments on this thread offers another option:

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

2016-12-03 Thread Paul Masson
There's apparently no good way in general to test whether the scene is unchanged. This is a known issue: https://github.com/mrdoob/three.js/issues/7670 One of the comments on this thread offers another option: only render the scene upon user interaction. I'm so accustomed to writing Three.js

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

2016-12-03 Thread William Stein
On Sat, Dec 3, 2016 at 1:11 PM, Volker Braun wrote: > Well if the scene is static, the controls didn't change, and the canvas size > didnt't change then your callback in requestAnimationFram should just do > nothing instead of repainting the unchanged scene, right? +1 --

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

2016-12-03 Thread Volker Braun
Well if the scene is static, the controls didn't change, and the canvas size didnt't change then your callback in requestAnimationFram should just do nothing instead of repainting the unchanged scene, right? On Saturday, December 3, 2016 at 9:46:50 PM UTC+1, Paul Masson wrote: > > > > On

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

2016-12-03 Thread Paul Masson
On Friday, December 2, 2016 at 11:47:40 PM UTC-8, tdumont wrote: > > > But why is three.js consuming cpu when the browser shouls have nothing > to do ? (no interaction). > There is a rendering loop that runs continuously to call requestAnimationFram(). This is a standard technique for

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

2016-12-02 Thread Thierry Dumont
Le 02/12/2016 à 23:43, Paul Masson a écrit : > 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

[sage-devel] Re: three.js on 7.5 beta 5: cpu...

2016-12-02 Thread Paul Masson
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