So I am going to add my very small two cents to this discussion. It is clear there is a lot of frustration based on the thread and rightly so, given what people pay for Apple products. I upgraded to Moutain Lion Day 1, and right away not only did I notice battery degradation - but my RPMs on the CPU were off the charts. I have a MacBook Pro 13 inch late 2011 model (purchased in Dec 2011).
Before this upgrade, I NEVER, let me restate that - NEVER heard my fans. I know they run but never heard the things going. All of sudden, fans are whirling, RPMs zooming and the tempature is climbing. In addition, as soon as I go off AC my battery tanks. Being new to Mac I have no idea what to do. For about two days, I have been searching the Internet trying to get a sense of how to troubleshoot the problem and subsequently fix it. I thought initially it might be due to the indexing happening from the new upgrade, but all the indexing had concluded so that wasn't it.
In the meantime, I am monitoring Activity Monitor, but there is absolutely nothing or rather no program that seems to be hogging up my CPU. I come to this forum and quite literally stumble upon someone posting about a process running called "bash". This is a process associated with Send to Kindle which I have on my Mac. You really wouldn't think this process would cause a problem because everytime I saw it, it was running between 6-8% of the CPU. Another person Fieldman indicated that this small process was contributing to heating and battery life. The advice was to un-install and see what happens. I un-installed the Send to Kindle app and within minutes, battery life returned, tempature dropped WAY DO and the fans went silent. It was unbelieveable how quickly it happened.
The machine has been running "like new" again and unless I have every app on my computer open, I haven't heard them since. The RPMs is down to around 1500-2000 and quite as a mouse. So I am back to right again, and hope many of you are able to find the culprit of your issues. Good Luck!
P.S. Since this - Fieldman posted and indicated that Amazon had fixed the problem so re-downloaded Send to Kindle app and all is still well!