Gtalk uses C2DM. What this means is it's essentially a shell on the phone. Not using battery, and using a tiny bit of resources (RAM). This process simply sits waiting for a message to be pushed from a cloud. It does not actively poll meaning it does not use any battery.
What will waste battery though is killing this process. Because this is an essential process for android, many features of the phone rely on it (market, gtalk, gmail). When you kill this process, it will inevitably start itself back up, again, because it's a crucial process. By constantly killing, respooling, killing, respooling you are wasting battery because it takes resources to kill something, then more resources to respool it.
This is a process you're best suited by leaving alone. And my recommendation, remove task killer and reboot phone. If you need some assistance understanding the memory handling of Android, there are some really great resources on the web you can read. What you'll find in conclusion of all of them is android handles memory very efficiently and the whole "windows" frame of mind of kill kill kill needs to be let go.
Thats not without saying though that a poorly designed app cant kill battery. Some examples are apps that use an improper wakelock, or an app that receives it's messages via polling. These will eat a battery quickly but the answer is, don't use that app. Find a messaging app that uses C2DM (like gtalk does). Or find an app thats doesn't have a wakelock issue, i think we all remember the facebook problem lol. That was due to a wakelock.
Hope this helps.
What will waste battery though is killing this process. Because this is an essential process for android, many features of the phone rely on it (market, gtalk, gmail). When you kill this process, it will inevitably start itself back up, again, because it's a crucial process. By constantly killing, respooling, killing, respooling you are wasting battery because it takes resources to kill something, then more resources to respool it.
This is a process you're best suited by leaving alone. And my recommendation, remove task killer and reboot phone. If you need some assistance understanding the memory handling of Android, there are some really great resources on the web you can read. What you'll find in conclusion of all of them is android handles memory very efficiently and the whole "windows" frame of mind of kill kill kill needs to be let go.
Thats not without saying though that a poorly designed app cant kill battery. Some examples are apps that use an improper wakelock, or an app that receives it's messages via polling. These will eat a battery quickly but the answer is, don't use that app. Find a messaging app that uses C2DM (like gtalk does). Or find an app thats doesn't have a wakelock issue, i think we all remember the facebook problem lol. That was due to a wakelock.
Hope this helps.
Facebook
Twitter
Instagram