Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mat-dev] Using MAT for Android

Hi Krum,

That's fine. We have several proposals ourselves, so we will have plenty to talk about as well.

FYI, I have a new post on the MOTODEV Studio blog this week on using MAT. It will also feature in our monthly developer newsletter next week.

Regards

-E

On Tue, Nov 30, 2010 at 4:35 AM, Tsvetkov, Krum <krum.tsvetkov@xxxxxxx> wrote:
Hi Eric,

I did, but I was a bit too late - the abstract is already submitted. It is on the topic of extending MAT but in a bit different direction. Here is the proposal which was made: https://www.eclipsecon.org/submissions/2011/view_talk.php?id=2184

I'd suggest that we wait for the session selection to finish. If the colleagues get the talk accepted, we can still discuss how to show something together.

Is this fine with you?

Sorry that it didn't work very smooth this time. I personally felt pretty happy about what you have achieved (with little effort) and would be happy to see it also as part of a talk.

And as I said in the beginning I'm also very interested what the feedback of the developers using the tool for memory analysis on mobile devices will be.

Regards,
Krum

-----Original Message-----
From: mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of ERIC CLONINGER
Sent: Dienstag, 30. November 2010 04:56
To: Memory Analyzer Dev list
Subject: Re: [mat-dev] Using MAT for Android

Hi Krum,

Did you make contact with your colleagues? Since Tuesday is the
submission deadline, I wondered if we need to come up with an
abstract. We have submitted talks for our projects, but if a MAT talk
does go through, we would be happy to talk about our experiences.

Regards

-E

--
Eric Cloninger (ericc@xxxxxxxxxxxx)
Senior Product Manager, MOTODEV Studio for Android
Eclipse Sequoyah Project Lead


>
> About EclipseCon - I like the idea to have a talk together pretty much, however, I am not going to the EclipseCon, and I think no one else from the team is going either.
> As far as I know, There will be 20 minutes sessions so probably this topic could fill one. Alternatively - I think there will be some other colleagues from SAP which will propose a talk about extending MAT to better express jruby contents in a heap dump. I can check with them what they think about mixing the two topics.
>
> I'll post again my first experience once I've tried the MOTODEV Studio / MAT stuff.
>
> Regards,
> Krum
>
> -----Original Message-----
> From: mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of ERIC CLONINGER
> Sent: Dienstag, 23. November 2010 17:20
> To: Memory Analyzer Dev list
> Subject: Re: [mat-dev] Using MAT for Android
>
> Ciao Gentlemen!
>
> I'll have to get the engineering team lead (Vinicius) to comment on
> the details of the integration. But, from my recollection, it wasn't
> terribly difficult to include in the product. I don't get to write
> code any more, so anything that takes less than 2 weeks is "trivial"
> :-)
>
> If you want to try it, download MOTODEV Studio at
> developer.motorola.com. It's free, but you have to create a
> registration to download. You can opt out of all communication from
> Motorola if you wish. Alternately, you can install Studio as plugins
> into your existing Eclipse.
>
> Once installed, we detect that the Android SDK is missing and use P2
> to retrieve it from Google's update site. Or, if you have the Android
> SDK already installed, just point to it.
>
> From the MOTODEV Studio perspective, you first create an emulator
> image (called an AVD). The first time you start the emulator, it takes
> ~5 minutes to unpack the filesystem and start QEMU. After that, it
> takes less time but it's not speedy by any stretch of the imagination.
>
> Create a sample app using (MOTODEV->New Project->From Sample).  Use
> the "Run as Android App with MOTODEV Studio" launch configuration.  At
> this point, from the device management view, you can select your
> emulator, right click, and choose (Analyze Memory with MAT).
>
> The resulting workflow runs HPROF and then MAT. The results are
> displayed in a window in the editing area. The HPROF generation for
> input to MAT is done by the Google DDMS tool and is exposed in their
> plugins. We added filtering so that the output focused solely on
> values of interest to the users' application and not other processes.
> We also simplified the workflow somewhat. I do know we added at least
> one button in the toolbar to handle OQL searches. But, I'll let Vini
> tell you the details.
>
> Are you attending EclipseCon? We thought it might be a good talk to
> present our adoption case. But, I don't think it would make a full
> session. If you are already proposing a MAT talk, we could provide
> some information on our adoption.
>
> Regards
>
> Eric
>
> --
> Eric Cloninger (ericc@xxxxxxxxxxxx)
> Senior Product Manager, MOTODEV Studio for Android
> Eclipse Sequoyah Project Lead
> _______________________________________________
> mat-dev mailing list
> mat-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mat-dev
> _______________________________________________
> mat-dev mailing list
> mat-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mat-dev
>



--
Eric Cloninger (ericc@xxxxxxxxxxxx)
Senior Product Manager, MOTODEV Studio for Android
Eclipse Sequoyah Project Lead
_______________________________________________
mat-dev mailing list
mat-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mat-dev
_______________________________________________
mat-dev mailing list
mat-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mat-dev



--
Eric Cloninger (ericc@xxxxxxxxxxxx)
Senior Product Manager, MOTODEV Studio for Android
Eclipse Sequoyah Project Lead

Back to the top