> Although this may be fast enough for many applications, it is
> much slower than dedicated C code (for example, a very lean
> single scope program, based on fltk [2], can easily show more
> than 90.000 pixels/second on the same PC).
Run "top" when you're executing the test. I found that almost all of the
overhead in my realtime linux/X systems is the X server. When the app
code and the X server are on the same machine, and I update "waveform
displays", the X server is the top cpu hog, and the driving code (client)
is very low on the list. I have display apps in both "C" and "Tcl/Tk/Blt"
and even the Tcl/TK code uses only a few percent of the CPU while the
Xserver can easily use 60-80%.
My partial solution was to run the Xserver on a networked laptop running
the Xserver as an X terminal with:
X -query realtime-machine.net
With:
X :1 -query realtime-machine.net
You can have one Xserver for the laptop, and the second one taking care of
the realtime-machine.net.
RT/linux is great!!!!!!! :-)
-C Wayne Wright
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
