Wt embedded » History » Revision 6
Revision 5 (Pieter Libin, 10/29/2009 02:59 PM) → Revision 6/31 (Pieter Libin, 10/29/2009 03:00 PM)
h1. Wt embedded
{{toc}}
Find here information on running Wt in resource constrained embedded systems: performance, code size, memory usage, and other info.
h2. General
Wt can easily be built for and deployed on embedded POSIX systems, such as embedded linux.
h3. Cross-building
Using CMake with a cross compilation environment: to be completed...
Instructions for cross compiling with cmake can be found on the "CMake Wiki":http://www.cmake.org/Wiki/CMake_Cross_Compiling. If you encounter the following error a workaround is to replace $Build/src/filetostring with a version compiled with your native compiler.
<pre>
/bin/sh: ./filetostring: cannot execute binary file
</pre>
h3. Optimizing executable size
Points to consider when optimizing the executable size:
* Choose build-type <tt>MinSizeRel</tt>
* Add extra compile FLAGS: <tt>-fvisibility=hidden</tt> (to avoid listing symbols in the executable)
* Add extra compile FLAGS: -DHAVE_GNU_REGEX to avoid the dependency on libboost_regex, when building on a system that is based on glibc or uClibc.
* _*Add extra compile FLAGS: -DNO_SPIRIT to not use spirit for parsing locale and cookies (FIXME: not yet supported)*_
* Build static libraries (for libwt.a and libwthttp.a)
* Disable build options you don't need and introduce extra dependencies (libz, openssl ?)
* Link statically to all libraries that you use only for Wt (such as for example the boost libraries). You will need to do this manually since this currently isn't supported in the CMake build process. In this way, only used symbols from these libraries (including the static wt and wthttp) will be kept.
* Strip your binary using <tt>strip -s</tt>.
* Optionally, when available for your platform, you may want to compress the size of your binary using the "Ultimate Packer for eXecutables (upx)":http://upx.sourceforge.net/. This typically reduces executable size further by 60-70%, without noticable run-time performance hits.
h3. Measuring performance
To report the run-time performance of Wt on a particular embedded platform, you must connect to the device using a local area connection (through at most one switch), and measure the time between transmission and reception of packets (using a packet sniffer). For the measurements, we use two examples that are included in the Wt distribution: "hello":http://www.webtoolkit.eu/wt/examples/hello/hello.wt (as an example of a minimal application), and "composer":http://www.webtoolkit.eu/wt/examples/composer/composer.wt (as an example of a simple, yet functional, application).
We propose to measure the time to create a new session, and the time of a small event.
h4. Runtime: new session
Wt starts a new session by serving a small page to determines browser capabilities, and then trigger a second call to get the "main page", that has all visible content. To compare the relative performance for a particular platform, you should measure this "load" time, as the total duration of these two requests. You should measure the time from sending the first request, to sending the third request. The third request is either a GET request for auxiliary content (CSS or images), a GET request to a Wt resource, or a POST request to load invisible content in the background.
h4. Runtime: event
We estimate the time needed to process a small event, such as a click on the "Greet me" button in hello, and "Save now" in composer, by measuring the total time for the packet exchange triggered by such an event.
h4. Memory usage: basis
Measuring memory usage is a tricky thing, since code and read-only data memory used by shared libraries is effectively shared between processes, while writable data segments are obviously private to each process.
Therefore, we use <tt>pmap</tt> to study the memory in different segments. The basis RAM usage is divided between read-only segments, and writable segments. Only the latter are really constrained by physical RAM. We get the total writable size. by summing the size of all writable segments, indicated by pmap with a *w*. The total size reported by pmap and top, minus the size of all writable segments is then the read-only RAM usage. Thus, this number includes shared libraries, and thus overestimates actual RAM usage.
h4. Memory usage: per session
Compare the memory usage after starting 10 sessions with base memory usage, and divide the difference by 10 to estimate the memory used by a single session.
h2. Platforms
h3. ARM926EJ-S
h4. Processor features
* Clock-speed: 200 MHz
* Linux BogoMIPS: 89.70
* Caches: 8K instruction, 8K data
h4. Config #1: minimal
h5. Setup
* *Wt version:* CVS-snapshot 18/03/08
* *Target system:* Linux uclibc 2.6.23
* *Build environment:* buildroot, arm-linux-gcc 4.2.1
* *Options:* with multi-threading, but without libz and OpenSSL
* *Build type:* full static build, except for: libc, libpthread, libdl, libstdc++, and libm
* *Build settings:* MinSizeRel, -DHAVE_GNU_REGEX
* *Runtime settings:* ./app.wt --docroot . --http-address 0.0.0.0 --threads=2 --no-compression
h5. Performance results
*Code size and RAM usage (in KBytes)*
|_.Program|_.Code |Program|Code size (strip)|_.Code (strip)|Code size (strip + upx)|_.RAM: upx)|RAM: basis † (read-only)|_.RAM: (read-only)|RAM: basis (writable)|_.RAM: (writable)|RAM: per session|
| hello| 1.130 | 304 | 2.580 | 372 | 28|
| composer| 1.265 | 332 | 2.712 | 372 | 126|
† includes shared libraries !
*Runtime-performance*
|_.Program |Program | _.New New session (http) | _.Event (http)| Event (http)
| hello | 0.58 s | 0.15 s |
|composer| 1.8 s | 0.15 s |