Re: EXE running from network share larger than EXE itself?

That's certainly one of my thoughts. I'm also surprised at the 309K of I/O reads, because
a 1.7MB executable should involve on the order of 1.7MB of data transmitted. I wonder if
the Process Explorer actually accounts for the reads required to initially load the image,
that is, what takes place before the process actually has an identity.

The fact of static linking seems largely irrelevant. There are loads of other DLLs
implicit in using MFC (I have an MFC app which is pretty vanilla which uses 26 DLLs by the
time OLE and other DLLs are taken into account). And some DLLs will be searched for on the
remote machine.

I'd suggest using something like FileMon on the remote machine to see what the I/O traffic
is. It might be revealing.
joe

On Tue, 14 Jun 2005 16:17:03 GMT, Geoff <geoff@xxxxxxxxxxxxxxx> wrote:

>On Tue, 14 Jun 2005 09:41:28 -0500, "Todd Brooks"
><tbrooks@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>>I've locked down the net analyzer to just between my workstation and that
>>standalone server...no other traffic should be between them besides your
>>standard network browsing (RIP?) broadcasts, which are small and infrequent.
>>
>>Keep in mind this is a statically linked EXE, thus there are no
>>dependencies, so unless the EXE is searching the EXE directory for system
>>DLL's, I'm not sure if that could be causing the excess traffic. Loading
>>the EXE locally, just starting up the app, only consumes 309K of I/O Reads
>>(according to SysInternals' Process Explorer).
>>
>>Any other ideas? My network is all Windows 2003 Servers, a single domain.
>>NetBIOS is enabled on my machine, everyone has static IPs (NAT'd).
>>
>>todd
>>
>
>How many page faults are generated during startup of your application?
>Windows could be discarding segments of your program and since paging
>of exe's involves discard/reload from the original file it may be
>re-transmitting segments of your program to satisfy the page loads.
>This is done in 4kB chunks.
>
>Perhaps sniffing the wire with Netmon might tell you what transactions
>are going on. You would also be able to get a handle on how much
>network overhead is involved.

Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.

Relevant Pages

  • Re: Advice Please
    ... Using a very basic install package and setting .net security properly, ... shouldn't have to install the dlls on the local machine. ... as a standalone exe file. ... the network and all the users can run the application. ...
    (microsoft.public.dotnet.languages.vb)
  • assembly deployment
    ... I have an application that resides on a network share. ... DLLs and 1 exe, ... all clients are able to run the app by simply ...
    (microsoft.public.dotnet.framework)
  • Re: Asus V9250 magic graphics driver - cant see adaptor in Contro
    ... This is a painstaking procedure as there are a lot of dlls and ... exe files to open in depends. ... only created on successful install which hasn't happened. ... driver inf file. ...
    (microsoft.public.windowsxp.embedded)
  • Re: C# Exceptions
    ... I did a runtime analysis of the exe and some important DLLs as ... > signature is valid then the app can decrypt the response and process it. ... > the source code of a managed app. ... NOT FOR THE MAIN PROGRAM EXE FILE. ...
    (Pen-Test)
  • My.Settings Thoughts
    ... was a GLOBAL shared memory map that allowed the EXE and her .NET dlls to shared this "namespace" ... But for the settings, it uses the same file, but the sections are different. ... To provide access to the EXE, I had created Get/Set properties but I did that in the Form partial class. ... That way it can be used by the application DLLs. ...
    (microsoft.public.dotnet.languages.vb)
Loading