On Sun, Feb 27, 2011 at 4:54 AM, Markus Junginger <[email protected]> wrote: > Since I updated ADT, I am experiencing CPU load issues. One of the > cores goes to 100% when I use the layout editor for a while. I am > running Windows 7, and a friend confirmed this issue with Linux. Is > there a known workaround?
Is there any way you can grab a few representative thread dumps while it's churning away so we can see what it's doing? ( jps -lm to find the process id, then jstack <pid> to get the thread dumps) ? > Also, at least when running Windows, the new palette looks shaggy due > to bitmap scaling issues. Yeah, that's Windows-specific and was just fixed ( https://review.source.android.com//#change,21495 ). > And speaking of ADT: are there any known plans to improve performance? > We have several larger project and every time we update a single file, > ADT seems to build the entire APK from scratch. This takes up to > almost a minute, which decreases productivity. The builder could be > more intelligent and just update the deltas. We definitely want to tune and improve performance. We have reports of projects getting to a certain size suddenly causing things to get very slow - we're investigating that. > Lastly, I am just writing an article on ADT, so I could mention some > future plans, if anyone from Google happens to read this. One focus area is the layout editor - but we're doing work in many other areas as well. On http://tools.android.com/recent you'll see some of things we've checked in since ADT 10 (though it's missing updates for the last couple of weeks - we've been working on some larger tasks.) -- Tor -- 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
