Tasker optimization (cpu, memory, response time etc)

[Antijape]

I've been using the software for a few months now and the profile
count (22) has been the same for a while. For the past days I've been
trying to minimize Taskers cpu/memory usage and at the same time
trying to improve response time and relialbility. I started from 6-7%
cpu usage and I'm now at 4-5%. This has been done mostly by "cleaning
the code" and by replacing some of the user-built techniques with
internal ones. I think one of the biggest things was buying the pro
version of Screebl so that now I can turn it off when I don't need it
(from Tasker). At the same time Taskers reliability has improved since
after the clean I haven't had as many "missfires" than before. The
program I've been using to monitor is Android Assistant. I'm not sure
how accurate the percentages are but I think it doesn't matter as long
as I use the same program for monitoring.

What I would like to know is that are there any basic rules/techniques
what should be avoided or preferred when building profiles on a "multi-
profile" system. For example is it better to have 2 profiles with same
context (like Phone ringing) or should I just call the second task
from the first one? Or what do you think is it better to disable
profiles that are not in use (for example disable day-profiles during
night) or does it have any effect at all? It would be nice to hear
your tips about how to get better performance and reliability with
minimun cpu use. Thanks!

-antijape

[BradM]

Just curious. In what situations would you turn off Screebl?

Brad

[TomL]

I did some tests, and it seemed that (=) math:equals was about 50%
faster than (~) string:matches. So, instead of:

if %MYVAR ~ 1

... I use...

if %MYVAR = 1

Tom

[Antijape]

Thanks TomL, thats a good tip. Something like this I was looking for!

Brad: for example in car. I drive a lot and phone is in dock with
screen on. I have a feeling this made quite a big improvement for
battery use. Not actually a Tasker improvement but still. I also turn
it off during night and after screen has been off more than 15min but
I'm not sure if Screebl even does anything while screen is off.

[Hagure]

I've been mulling over writing a similar post to this one for a while
now.
Running a D1, I run into "low memory" errors all the time, and am
trying to do a clean-up as well.

It would be awesome if there was a "memory use guide" to the various
Tasker features, kind of like the one LauncherPro has going for it
here: http://www.launcherpro.com/forum/viewtopic.php?f=6&t=2344

PS: Good tip about MATH= vs. Matches. I always figured this would be
the case!