Re: Why is the CE 6 emulator so slow?

Hang on, you're talking about a debug image. Yes, those are slow.
Incredibly so in CE6 (on real devices, I assume that is the case in the
emulator as well but I never do it so I can't say definitively).

What is the performance like in a retail emulator build?

--
Dean Ramsier - eMVP
BSQUARE Corporation


"charlez mutton" <charlezmutton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9DB3332E-2800-475D-896C-2F7F3E18EEB9@xxxxxxxxxxxxxxxx


"<ctacke/>" wrote:

Is there more than one? I thought there was only the ARM emulator.

You thought wrong. There are a few versions of Device Emulator (3 I
believe).

There are? Where can I find info on those? All I've seen is the one: the
ARM
emulator.



This is an image that I built but is pretty much a vanilla network
appliance
style build, pretty much the same as Mike Hall used in his video.

CPU activity drops to close to zero when there is no UI activity so it
would
seem there are no silly backgroungd threads running.


But the fact that it's very slow indicates that something is going wrong.
You're also looking at CPU activity of the host PC, not the actual
device,
which is not necessarily the same.

I looked at both and they match pretty closely,so I think they are in
sync.

A debug image would be of great use
here.

I am using a debug image.

Using kernel tracker would probably help too.

I did and I'm seeing the same % numbers.

If you created the
image then there are several tools that you have to see what the OS is
doing.

Here's what I see:
* Actual load is pretty quick. A few seconds to load the image.
* Boot (emulator launched and loaded until main WInCE window and
chime)
takes approx 5 minutes.

This indicates a problem. Again, the debug output will give you a lot
more
information than a stopwatch.

The CPU usgae monitor is showing the same CPU usage.


* Launch the file explorer and painting the window it takes approx 1
minute.
Same again for entering a directory.

Again, this indicates a problem, and without debug output it's only blind
guessing as to what that problem might be.

* Stepping a driver in VS takes approx a second.

So you're attached with KITL already? That means you are already seeing
the
debug stream. What is it telling you?

Nothing really. Bunch of driver loads etc. Nothing odd coming out when
doing
the loads.



I notice that the emulator only uses one core in a dual core CPU and
about
80%-90% of that is being soaked up. CPU usage drops to 3% or so when
the
UI
is idle.

Sure, the CE OS isn't set up for using multiple processors, and it's
unlikely the emulator is either.

*What sort of speed do you see?

It's not as fast as a device, but not greatly different. Load one of the
Windows Mobile emulators and see how they run. They are using the same
emulator code, just with WinMo device images.

* What sort of speed should I expect?

The same as the WinMo stuff - maybe faster if you're doing less. Maybe
slower if you're doing more. Speed is subject to a lot of variables,
none
of which we know about your system.

* What can I do to speed this up? Or alternatively what can be screwed
up?

Find out what's going wrong by debugging with the tools. My telekinesis
powers are a bit lacking lately so I can't remote view what your OS is
doing
or what PB is telling you.

So what kind of things can you look at?


Perhaps I've screwed up a setting or perhaps I am spoilt from using
other
development environments.

Perhaps. Again, we know absolutely nothing about what you've done, what
BSP
you're using, what image contents you have, what drivers are loaded or
anything. The number of things that might be wrong is nearly infinite,
and
it may well (and likely is) something very simple. However only the
person
sitting at the development PC reading the information the tool is giving
has
any hope of determining what that problem might be. We can help, but
only
when provided information. An analogy to what you've told us would be
something like this:

I have a car. It has a motor. On a 6 lane interstate I can only go
30mph.
I once drove a sports car and it was fast. Why is my car slow? Is it
because my cars manufacturer did something wrong?

Thnak you for your info, but this is not so. I've built pretty much the
stuff that Mike built in the video.

I haave added an FSD but that is not active (I know ehn it is active
because
of debug tracing).


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com






.

Relevant Pages

  • Re: Why is the CE 6 emulator so slow?
    ... Hall has done many videos and created many emulator images. ... Provide the debug output. ... CPU activity drops to close to zero when there is no UI activity so it ... A few seconds to load the image. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Why is the CE 6 emulator so slow?
    ... There are a few versions of Device Emulator (3 I ... You're also looking at CPU activity of the host PC, not the actual device, ... I am using a debug image. ... A few seconds to load the image. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Why is the CE 6 emulator so slow?
    ... emulator as well but I never do it so I can't say definitively). ... The retail build fails while compiling, but a full debug build does ... CPU activity drops to close to zero when there is no UI activity so it ... A few seconds to load the image. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Why is the CE 6 emulator so slow?
    ... emulator as well but I never do it so I can't say definitively). ... The retail build fails while compiling, but a full debug build does ... CPU activity drops to close to zero when there is no UI activity so it ... A few seconds to load the image. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: WINDOWS CE 6.0
    ... Explorer shell to load. ... unless you want to debug. ... build your first run-time image. ... Windows Embedded Virtual ...
    (microsoft.public.windowsce.platbuilder)
Quantcast