Build by default with optimization level -O2 for GCC

before -O0 was used by default, that caused pretty bad performance.

Amd64, i6700k, 4200MHz, GNU/Linux (non-RT kernel), gcc 7.2.0

-------------------------------------
Optimization | EN/ENO |no EN/ENO |
-------------------------------------
default | 11 | 9.5 |
-O3 | 3.9 | 5.2 |
-O2 | 4 | 4.8 |
-Os | 4.1 | 3.5 |
-Ofast | 3.9 | 5.2 |
-------------------------------------

ARM, BBB Cortex-A8, 600Mhz, GNU/Linux, gcc 4.6.3

-------------------------------------
Optimization | EN/ENO |no EN/ENO |
-------------------------------------
default | 273 | 226 |
-O3 | 141.8 | 106.2 |
-O2 | 142 | 107 |
-Os | 152.5 | 112.2 |
-Ofast | 141.7 | 106.2 |
-------------------------------------

For embedded systems with size constaints (like Cortex-Mx, AVR and so
on) I usually use -Os. It gets pretty good results. For
GNU/Linux-based systems -O2 is usually a good choice, as you see the
test results.

     1

# those files are used in runtime

     2

# licensed according to LGPL, see COPYING.runtime 

     3

     4

images/icostop24.png

     5

images/icoplay24.png

     6

images/brz.png

     7

util/__init__.py

     8

util/paths.py

     9

runtime/WampClient.py

    10

runtime/PLCObject.py

    11

runtime/NevowServer.py

    12

runtime/webinterface.js

    13

runtime/__init__.py

    14

runtime/ServicePublisher.py

    15

runtime/typemapping.py 

    16

runtime/loglevels.py 

    17

Beremiz_service.py