Old VMS guy here. Threads are contained within a single process, i.e. not scheduled separately. Let me point out to things you could check out. First, the NDK could help you on the performance side. Second, if you want to run an activity in a separate process, use the android:process=":<activity name>" tag (this is set in AndroidManifest.xml). This will launch an activity as a separate process (i.e. will show as a separate process when you run a # ps)
On Apr 21, 8:15 pm, BobG <[email protected]> wrote: > I have this audio analyzer app that fills a buffer with audiorecord, > runs it thru a bunch of filters, and plots the filter out as a bunch > of vertical bars. I timed the sampling, filtering and drawing with > systemTimeMillis and it takes about 100ms,900ms and 50ms. I cant see > how putting the calcs in another thread could speed it up any, but I'm > just an old embedded c programmer. I guess linux is ticking every > millisecond, and there must be a dozen linux tasks running, and I > guess a task has a 'quantum' of ticks that it runs before linux > preempts it (anyone know about these details?), but I just want it to > run about 5 or 10 times faster. Appreciate any hints, tips, tricks, > etc. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group > athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
