Re: vc++ mfc project build is extremely slow taking hours

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Do you use precompiled headers? It could be that if all your CPP files are #including the same .h files, that loading those files over and over again (over the network) is what's causing a part of the slowdown. Things might speed up a bit (both over VPN and locally) if you switch to using precompiled headers and move all those common #includes into the precompiled header file.

"dwaach" <xbhishek.xsthxnx@xxxxxxxxx> wrote in message news:1ee586e7-5430-4357-aaaf-ab57b573d4f8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 9, 9:30 pm, "Tom Serface" <tom.nos...@xxxxxxxxxxxxx> wrote:
In addition to what other's have mentioned, are you running on VPN? I've
found that things can slow down quite a bit when running under VPN
especially if VS feels the need to get new source or check out files from
VSS.

Also, even though I don't like mapped drives, if you map drives to your
network shares things will run much faster.

Tom

"dwaach" <xbhishek.xsth...@xxxxxxxxx> wrote in message

news:5524042c-9c0a-4369-9421-5da33a83995a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



> Hi,

> I have a vc++ 2002.NET MFC console exe project and it accesses a lot
> of 3rd party headers and libraries available on a network machine \
> \dataread. Now, I do connect to that machine by Start->Run->\\dataread
> and entering user/pwd. Further I have declared several environment
> variables which are used in the Visual Studio project.

> The project build is extremely slow. I do not understand why ? It
> takes soe over 1 hour.

> Any help please appreciarted.

> Thanks,
> Abhishek- Hide quoted text -

- Show quoted text -

Hi,

Ya, I am using VPN as Cisco VPN to connect to the office network from
other place. Just missed to mention, when I compile the project while
at office the speed of compilation is avg around 5 mins. However, when
I do the same compilation from some other place than office, I usually
connect using Cisco VPN and then when I compile it takes around 1
hour.

I tried getting all the files locally on my system (those being
accessed using \\ path on network) and then too the compilation speed
is not too resonable when from other place than office.

Do we expect speed of acess reduction of '\\server' stuff when on
VPN ? Network shares do not work in VPN from other place. I tried them
but failed.

Any ideas why ?

Thanks
Abhishek

.

Relevant Pages

  • Re: vc++ mfc project build is extremely slow taking hours
    ... How sophisticated are the "third party" libraries. ... in slower compilation, but not an hour. ... How fast is your network and file server? ... I am using precompiled headers and the environment variables point to ...
    (microsoft.public.vc.mfc)
  • Re: vc++ mfc project build is extremely slow taking hours
    ... VPN can be miserably slow. ... in slower compilation, but not an hour. ... How fast is your network and file server? ... I am using precompiled headers and the environment variables point to ...
    (microsoft.public.vc.mfc)
  • Re: vc++ mfc project build is extremely slow taking hours
    ... network shares things will run much faster. ... I am using VPN as Cisco VPN to connect to the office network from ... I do the same compilation from some other place than office, ...
    (microsoft.public.vc.mfc)
  • Re: vc++ mfc project build is extremely slow taking hours
    ... Be aware that TCP MTU may be less on VPN interface. ... network shares things will run much faster. ... I do the same compilation from some other place than office, ...
    (microsoft.public.vc.mfc)
  • Re: [Full-disclosure] Remote Desktop Command Fixation Attacks
    ... This set of steps is redundant in many places, and it's also enormously expensive, since you're using no less than three different expensive bits of networking hardware (AP, PIX, VPN Concentrator), in addition to a bunch of x86 server hardware, windows server licenses, and at least one ISA license. ... Your computers necessarily don't have full access to your network infrastructure when they aren't logged on, so GPOs, software updates, etc can't be applied at the times you want them to be applied. ... Turning on, enabling, and implementing every possible security setting and device you think of is not defence in depth, and will probably only have two effects - your users won't use your wireless network, and you'll burn so much cash you won't have any left to spend on *useful* security measures. ...
    (Full-Disclosure)