Something funny happening with this patch during enlightenment window resize animations, I need to investigate.

This patch doesn't stand alone, and can't be landed without another patch in the series I'm reworking.

no change, something randomly broke during upload

no change, something randomly broke during upload

no change, something randomly broke during upload

no change, something randomly broke during upload

no change, something randomly broke during upload

Seems to work, shaves about 50ms off elementary_test startup for me here, so if you don't need the frame this can be a big win.

Looks like a good clean up to me.

Yep, looks waaaay better. elementary's list activity is a drop in the bucket now, as far as I can tell.

Fix the parent test to use parent and child instead of parent and self

What's broken? I seem to be able to navigate that test just fine?

Ooops, I think this one stayed the same and got rolled in with the new submissions

Just looking at elm_test startup, that list is *always* empty, so there would be a big payoff (probably another 2-3ms at elm_test start) moving that into the same list walk, nice catch.

Ah, cool, I didn't realize the list was usually NULL - I noticed there are fewer calls to _tree_custom_chain_missing(), so wondered if we frequently avoided non-NULL work there...

Adding cedric as a reviewer. If this is the wrong approach maybe he can give input on fixing it...

Tizen also doesn't frequently resize clients, as they're all full screen?

I thought about mashing _tree_custom_chain_missing() into this same loop, but it seems a little heavier, and I don't know if it would be a win 100% of the time.

Looking at before and after perf reports, I guess perf isn't actually the best way to show the benefit of that work - for elementary_test, eet wasn't prevalent in the report, and for a simple hello world eet is still the most prevalent thing in the report, just differently. :)

I've been looking at eet's contributions, as it was doing a lot of extra work at startup. Now that I've landed some eet fixes, here's the top few results I get from the perf report for:
ELM_FIRST_FRAME=E ELM_ENGINE=buffer perf record -i elementary_test

This makes sense to me.

Only add to freelist if allocation took place

This one breaks the test suite. revising.