On Tue, 29 Nov 2011 19:51:26 +1000 David Seikel <[email protected]> said:
> While I'm happy that EFL is working on the tiny little embedded 800MHz > 486 board, it might be a tad underpowered. > > At one point during this devices typical usage, it has to send stuff to > a serial printer, play a sound (through a USB based built in sound > chip), AND do a simple edje animation. At other times, it might be > doing one of the more complex animations, but need to play a short > sound on demand. The printer is kinda fussy about the timing of stuff > sent to it. are you doing this all from a single process? > After a short bit of testing, the sounds sometimes stutter quite badly > during the heavier animations, but is smooth during the others. > However, this is in a test mode, where there is more stuff on the > screen to slow things down. if you used a thread for audio (very good idea for things like audio) you want it to have a much higher priority than the rest of the app too so cpu cycles are allocated to it instead of to rendering or something else, when it needs it. in fact this is probably the 1 best idea of something like pulse audio.. as it is a separate process... it can run with a much HIGHER priority than other processes (nice -19 for example)... or even use root privs to get fifo realtime priorities. the only thing that can out-execute such a process is the kernel itself. > It's my understanding that edje runs in the idler, so shouldn't the > sound and printer, which both use ecore FD handlers to know when it's a > good time to write, have priority? no... edje does not "run in the idler". it does some things in jobs, some things in event handlers and callbacks from evas, and some in evas_render time - when evas asks edje to recalc before render... and then evas spends a lot of cycles rendering stuff. > I can probably fine tune things enough with judicious edje freezes, or > frame time, or something. It does not really matter if the animations > are a little jerky, might not even be noticeable, but the sound and > printing have to be spot on. > > Any hints from those more experienced with edge and FD handlers? threads or separate process and ipc to it. separate process with realtime fifo priority is the best. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
