Famous Engine - MOST STABLE RELEASE HERE

[roblav96]

THIS IS NOT OFFICIAL

Throughout the week I've been experimenting with different versions of Famous Engine to find one that's bug free. All versions I tested were consuming an absurd amount of CPU usage. Except one.

http://code.famo.us/famous/0.5/famous.min.js

That one there has been proven to be by far the most stable release I could find. I'm absolutely in love with this engine and I can't believe development has been put to a hult. For anyone having issues with the engine, just use this one. Thank you.

[CompSciFutures]

Hi Rob,

I think we are working on the same problem, this info is definitely useful.

Did you perchance make a test harness for experimenting with this that you
can share with me? I've been working on a performance problem that sounds
similar, might have a fix.

ap

On Tue, Nov 10, 2015 at 1:33 PM, Rob Laverty notifications@github.com
wrote:

THIS IS NOT OFFICIAL

Throughout the week I've been experimenting with different versions of
Famous Engine to find one that's bug free. All versions I tested were
consuming an absurd amount of CPU usage. Except one.
http://code.famo.us/famous/0.5/famous.min.js

That one there has been proven to be by far the most stable release I
could find. I'm absolutely in love with this engine and I can't believe
development has been put to a hult. For anyone having issues with the
engine, just use this one. Thank you.

—
Reply to this email directly or view it on GitHub
#504.

[roblav96]

It all started out when I pushed my app to iOS development stage and noticed extremely high CPU idle usage in the xCode monitoring suite. I was using the most recent 0.7.1 release in my browserify build. I started searching for any official stable release and came across this one on the FAQ page.

Sure enough, after converting everything to a global build, everything worked amazingly!

[CompSciFutures]

Hi Rob,

Thanks for the clarification, my experiences are much the same. I'll take a
look at 0.5.

ap

On Mon, Nov 16, 2015 at 7:32 PM, Rob Laverty notifications@github.com
wrote:

It all started out when I pushed my app to iOS development stage and
noticed extremely high CPU idle usage in the xCode monitoring suite. I was
using the most recent 0.7.1 release in my browserify build. I started
searching for any official stable release and came across this one on the
FAQ page.

Sure enough, after converting everything to a global build, everything
worked amazingly!

—
Reply to this email directly or view it on GitHub
#504 (comment).

[roblav96]

I have noticed that using the 0.5 version here in a browserify bundle still persists the problem. I would say just use the one I posted and have clarity knowing it will work. I've done a lot of testing with this and I am sure of the stability of this one.

[Arnleif]

Hi.

I'm not sure if this is related to your slowdown, but it could be.

in core/Transform.js multiply (out, a, b) function (In Famous, latest version)

there are lines like this:
changed = changed ? changed : out[0] === res;

which is wrong as changed will be true if there were no changes.
out[0] !== res;
would be correct.

This bug leads to all nodes/transforms having their update and/or (?) transform calculation called every frame.

Looking at the same file in 0.5, that function does not exist. It seems to have been introduced in 0.6

A

[roblav96]

How might one go about fixing this problem??? I would love to take a peek at it.

Are you saying all of the out[x] !== res?

[roblav96]

I have noticed a slight boost. I'm gonna profile it and see.

[CompSciFutures]

Took a quick look and have observed this change reducing the size of the famous.core.FamousEngine._messages array by ~50%

[roblav96]

Confirmed here as well!

[Arnleif]

Yeah, all of those out[x] !== res in the multiply function.

But there are more problems as those compares are exact and since some positions sometimes are floaty, the compare still comes out as 'changed'.

In one of my cases the one of the out[x] is 1085 and res 1085.0000305175781
And everything should be standing still..

But there must be other things also spending the cpu as the 0.5.2 version uses 0-2ms on while the 0.7 version uses 20-30 ms with my fix..

[roblav96]

How were you able to build 0.5.2 from npm? I get dependency errors as one of them were deleted from npm.

[speigg]

Just curious: is anyone planning on actually forking famous & maintaining these fixes? I already know about https://github.com/infamous/famous-engine, but that fork is not being maintained.

[ManuelOverdijk]

@speigg have a look at https://github.com/dmvaldman/samsara

[arunabhdas]

@roblav96 Yes I agree that the 0.5.x release is the most stable version. It definitely make sense to continue this project and see it through till completion.

[speigg]

@ManuelOverdijk Yes, I know about samsara. But that's based on famous 0.3 (pre-mixedmode), which was really entirely different (no webgl, no decoupling between the scene graph ui thread and the rendering pipeline, etc).