1 © 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

Cedric Bail – Senior Open Source Engineer

Samsung Research America (Silicon Valley)

cedric@osg.samsung.com

2

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

Speed

3

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

Benchmarking :Expedite: benchmarking only Evas directly

Improvement, expedite now use Ecore mainloop and Evas

Can now be used to benchmark Edje and Elementary (If someone write a test)

Now only use Eo API, so every release of EFL require some change in expedite

Doesn't benchmark energy consumption

Speed of 1.7 vs 1.8 was a 5% to 7% speedup in favor of 1.8 (After some work)

4

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

expedite -e software_x11 -a expedite -e opengl_x11 -a

EFL 1.8 404.23 55.46

EFL 1.9 402.02 55.22

EFL 1.10 397.93 55.41

EFL 1.11 398.42 55.95

master 389.89 55.98

5

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

Memory

6

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

Still mostly an expedite benchmark with massifWould be nice to cover edje/elementary...

Would be nice to ingrate memory consumption directly into it

Missing mmap area from massif report

7

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

expedite -e software_x11 -a expedite -e opengl_x11 -a

EFL 1.8 8.6MB 68.7MB

EFL 1.9 8.6MB 68.8MB

EFL 1.10 11.1MB 69.0MB

EFL 1.11 11.2MB 68.9MB

master 14.4MB 69.9MB

8

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

So !Getting fat around 1.10 is mostly linked to the addition of filter

There is more, but nothing clear

Getting fat in master, seems related to a change in behavior regarding font

Need investigation

9

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

10

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

11

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

12

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

Time to first frame

13

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

Time to first frame is important for SamsungNo real app benchmark

No hardware representing the potential issue

Currently running terminology and elementary_test under valgrind to have some kind of benchmark.

Doesn't simulate slow hard drive...

14

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

elementary_test ELM_ACCEL=none ELM_ACCEL=gl

EFL 1.8 7.04s 13.37s

EFL 1.9 7.51s 13.92s

EFL 1.10 8.91s 14.82s

EFL 1.11 9.25s 15s

EFL 1.12 10.93s 16.65s

15

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

terminology ELM_ACCEL=none ELM_ACCEL=gl

EFL 1.8 4.78s 10.54s

EFL 1.9 4.78s 10.72s

EFL 1.10 5.71s 11.31s

EFL 1.11 5.68s 11.46s

EFL 1.12 6.74s 12.71s

16

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

So :EFL application is slowing down since 1.10

Related apparently to something in edje and eet doing string check

Did someone notice ?

Need more time to investigate what is going on

Not a really relevant test as it is artificially slowed down

Better having an ARM based hardware that would be more realistic

17

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

Conclusion

18

© 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Performance review of EFL since 1.8

StillBlind to change during our fast development cycle

Nobody and nothing has time to check this

We are getting slower and fater over time if we don't check

Our tool are lacking information

• No view on mmaped area

• No analysis on process wakeup

• No analysis on time from input to result on screen

• No check on the result

We have one server sitting idle with a GPU and nothing else to do !

19 © 2014 SAMSUNG Electronics Co.Open Source Group – Silicon Valley

Thank you.