Proper Machine for Development

  • Thread starter Thread starter SH
  • Start date Start date
S

SH

I'm presently developing an application for a Pocket PC using the VS2005
Pocket PC 2003 emulator. My development machine is a Dell Pentium 4
running at 2.9Ghz with 1GB memory. Yet the development cycle (compiling,
deploying, etc) is painfully slow (even with all other applications closed).

What would you recommend for a proper development machine?

Thanks
 
I found the emulators a bit painful to use, other than that nothing
really wrong with the basic machine spec. Check what other processess
are running, possibly you are loosing all your resources to something
else. Ultimately, do an fdisk, always works wonders!

Chris
 
I'm using a machine significantly slower than that. What, specifically, is
causing most of the problem (this is just like optimizing your own code: you
start with the place where most of the time is being actually spent,
optimize that, then move on)?

Paul T.
 
The whole compile & deploy cycle. This is true even on repeating a
cycle, so everything is already in memory. Sure, repeats are a little
faster, but not by much.

I'm talking about a very simple program, nothing fancy. But it is
reading an xml file off a server and parsing it. Maybe that's it. I'll
take out that code and see what happens.
 
That's like saying "the whole program is too slow". It's interesting, but
totally useless, information. If you just compile, how long does that take?
Deploy, as a separate operation, takes how long? I'm not a mind-reader and,
as far as I know, neither is anyone else here. Are you going to help us
help you or not?!

Paul T.
 
SH said:
I'm presently developing an application for a Pocket PC using the
VS2005 Pocket PC 2003 emulator. My development machine is a Dell
Pentium 4 running at 2.9Ghz with 1GB memory. Yet the development cycle
(compiling, deploying, etc) is painfully slow (even with all other
applications closed).
What would you recommend for a proper development machine?
Click to expand...

I'd be interested to see what others recommend but that spec is better than
my laptop (2.8 ghz 500MB) and while I wouldn't say it 'flies' I've got no
particular problems with VS2005 compiling/deploying even with other apps
running.

Regards

Will Chapman
 
OK, OK! I misunderstood what you were after. Geeee.

The initial compile & deploy requires 55 seconds. On subsequent compile
& deploys it takes between 15 & 20 seconds for the program to start.

Now that I've done the timing, I see that a compile alone takes 3-5
seconds. A deploy alone takes 8-10 seconds. The rest of the time must be
the app coming up on the emulator.

Hope that's the info you want.
 
We *have* to separate compile from deploy! Ctrl+Shift+B will do the compile
only. You can use the Deploy item on the menu to do just that. Are you
running in the debugger or just telling the application to launch with no
debugging? Are both your application and the .NET CF itself being deployed
to the emulator? I don't use emulators much, but it seems like you should
be able to leave the emulator in a state where everything is still installed
from the last time.

3-5 seconds seems perfectly fine to me for compile. 8-10 seconds is also
reasonable for a deploy. The startup of for .NET CF applications is known
to be noticably long. .NET CF 2.0 should be faster than .NET CF 1.0. What
you see on the emulator is likely to be consistent with what you'll see on a
real device, although the real device may not take absolutely as long to
launch the program.

Paul T.

SH said:
OK, OK! I misunderstood what you were after. Geeee.

The initial compile & deploy requires 55 seconds. On subsequent compile &
deploys it takes between 15 & 20 seconds for the program to start.

Now that I've done the timing, I see that a compile alone takes 3-5
seconds. A deploy alone takes 8-10 seconds. The rest of the time must be
the app coming up on the emulator.

Hope that's the info you want.
That's like saying "the whole program is too slow". It's interesting,
but totally useless, information. If you just compile, how long does
that take? Deploy, as a separate operation, takes how long? I'm not a
mind-reader and, as far as I know, neither is anyone else here. Are you
going to help us help you or not?!

Paul T.

The whole compile & deploy cycle. This is true even on repeating a cycle,
so everything is already in memory. Sure, repeats are a little faster,
but not by much.

I'm talking about a very simple program, nothing fancy. But it is reading
an xml file off a server and parsing it. Maybe that's it. I'll take out
that code and see what happens.


Paul G. Tobey [eMVP] wrote:

I'm using a machine significantly slower than that. What, specifically,
is causing most of the problem (this is just like optimizing your own
code: you start with the place where most of the time is being actually
spent, optimize that, then move on)?

Paul T.



I'm presently developing an application for a Pocket PC using the
VS2005 Pocket PC 2003 emulator. My development machine is a Dell
Pentium 4 running at 2.9Ghz with 1GB memory. Yet the development cycle
(compiling, deploying, etc) is painfully slow (even with all other
applications closed).

What would you recommend for a proper development machine?

Thanks
Click to expand...
Click to expand...
Click to expand...
 
To be honest under VS2005 that seems perfectly resonable. The new emulators
are so much more resource hungry because they have alot more functionality
built into them.

You will find your device runs faster than the emulators in VS2005 but the
reverse with VS2003.

I use nothing but the device for testing as it gives me a much more accurate
reading, plus it's faster.

SH said:
OK, OK! I misunderstood what you were after. Geeee.

The initial compile & deploy requires 55 seconds. On subsequent compile &
deploys it takes between 15 & 20 seconds for the program to start.

Now that I've done the timing, I see that a compile alone takes 3-5
seconds. A deploy alone takes 8-10 seconds. The rest of the time must be
the app coming up on the emulator.

Hope that's the info you want.
That's like saying "the whole program is too slow". It's interesting,
but totally useless, information. If you just compile, how long does
that take? Deploy, as a separate operation, takes how long? I'm not a
mind-reader and, as far as I know, neither is anyone else here. Are you
going to help us help you or not?!

Paul T.

The whole compile & deploy cycle. This is true even on repeating a cycle,
so everything is already in memory. Sure, repeats are a little faster,
but not by much.

I'm talking about a very simple program, nothing fancy. But it is reading
an xml file off a server and parsing it. Maybe that's it. I'll take out
that code and see what happens.


Paul G. Tobey [eMVP] wrote:

I'm using a machine significantly slower than that. What, specifically,
is causing most of the problem (this is just like optimizing your own
code: you start with the place where most of the time is being actually
spent, optimize that, then move on)?

Paul T.



I'm presently developing an application for a Pocket PC using the
VS2005 Pocket PC 2003 emulator. My development machine is a Dell
Pentium 4 running at 2.9Ghz with 1GB memory. Yet the development cycle
(compiling, deploying, etc) is painfully slow (even with all other
applications closed).

What would you recommend for a proper development machine?

Thanks
Click to expand...
Click to expand...
Click to expand...
 
Hi all.
I have been using P4 1500 with 384 memory for development for last couple of
years and
this year I have changed the machine to P4 3000 1Gb memory,
and have to say that emulator can't be used at all, it is too slow, I am
using real device
in my work it saves the time on deploying, running and testing.
 
Also I feel like to add that last days I am writing the app and test it on a
desktop then
I am recompiling it for PocketPC and test on a real device (iPAQ 2200) so
only last
development cycle requires usage of PocketPC it really saves a lot of time
and nerves :)
for development
 
I also found that defraging my hard drive made things noticeably faster.
We *have* to separate compile from deploy! Ctrl+Shift+B will do the compile
only. You can use the Deploy item on the menu to do just that. Are you
running in the debugger or just telling the application to launch with no
debugging? Are both your application and the .NET CF itself being deployed
to the emulator? I don't use emulators much, but it seems like you should
be able to leave the emulator in a state where everything is still installed
from the last time.

3-5 seconds seems perfectly fine to me for compile. 8-10 seconds is also
reasonable for a deploy. The startup of for .NET CF applications is known
to be noticably long. .NET CF 2.0 should be faster than .NET CF 1.0. What
you see on the emulator is likely to be consistent with what you'll see on a
real device, although the real device may not take absolutely as long to
launch the program.

Paul T.

OK, OK! I misunderstood what you were after. Geeee.

The initial compile & deploy requires 55 seconds. On subsequent compile &
deploys it takes between 15 & 20 seconds for the program to start.

Now that I've done the timing, I see that a compile alone takes 3-5
seconds. A deploy alone takes 8-10 seconds. The rest of the time must be
the app coming up on the emulator.

Hope that's the info you want.
That's like saying "the whole program is too slow". It's interesting,
but totally useless, information. If you just compile, how long does
that take? Deploy, as a separate operation, takes how long? I'm not a
mind-reader and, as far as I know, neither is anyone else here. Are you
going to help us help you or not?!

Paul T.



The whole compile & deploy cycle. This is true even on repeating a cycle,
so everything is already in memory. Sure, repeats are a little faster,
but not by much.

I'm talking about a very simple program, nothing fancy. But it is reading
an xml file off a server and parsing it. Maybe that's it. I'll take out
that code and see what happens.


Paul G. Tobey [eMVP] wrote:


I'm using a machine significantly slower than that. What, specifically,
is causing most of the problem (this is just like optimizing your own
code: you start with the place where most of the time is being actually
spent, optimize that, then move on)?

Paul T.




I'm presently developing an application for a Pocket PC using the
VS2005 Pocket PC 2003 emulator. My development machine is a Dell
Pentium 4 running at 2.9Ghz with 1GB memory. Yet the development cycle
(compiling, deploying, etc) is painfully slow (even with all other
applications closed).

What would you recommend for a proper development machine?

Thanks
Click to expand...
Click to expand...
Click to expand...
 
Back
Top