From: Geoff Schaller on
Dirk,

It isn't a Microsoft problem. I will say it again: we have plenty of
situations where an exe and its DLLs are launched across a network and
there is zero difference in load time. Zero. It will be wholly a
property of your application. One way to prove it? Create a tiny exe
that does no data loading. Link it in to your libs so that it is large.
Test that out.

Geoff




__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3694 (20081215) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


From: Geoff Schaller on
Actually the reverse should be true. A share is resolved at login
whereas a UNC is re-evaluated on every use.


"Marc Verkade [Marti IT]" <marcatM(a)rtidotnl> wrote in message
news:49477e2b$0$765$58c7af7e(a)news.kabelfoon.nl:

> Hai,
>
> We have seen that communicating through a share F:\App.exe works slower than
> using an UNC path like \\serverip\appshare\app.exe
>
> Perhaps worth a try.
>
> --
> Grtz, Marc


__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3694 (20081215) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


From: Phil Mermod on
Hi Dirk,

I posted in this thread a trick related with your (a) and (b).

Did you try it ?

--
Phil Mermod
Crystal Reports Library for Visual Objects
http://www.pkl.ch/dev/


Dirk (Belgium) wrote:

> Paul D B wrote:
>
> > Dirk
> >
> > Hi Dirk, well you have done some precise testing now and
> > this allows you to pinpoint several problems. I must admit
> > that the difference between:
> > > local exe + local dbf + empty dbf = 3312 milliseconds
> > and
> > > network exe + local dbf + empty dbf = 7108 milliseconds
> >
> > is surprising, given the fact that the application is
> > already loaded in memory and that these timings are for the
> > opening of a childwindow only (but that was your initial
> > problem and question, and I have no answer for that).
> >
> > But it is clear that you have to redesign your window which
> > is overloaded. Not easy, I've got a few similar windows
> > (also with several tabs that all have browsers and all share
> > the same servers) and the fact that you are sharing servers
> > between the subpages and that they communicate which each
> > other, makes it quite difficult to redesign it. But it is
> > clear that you should go to an approach where you only open
> > the servers and browsers when the user opens that tabpage.
>
>
> Paul,
>
> Redesign will be done next month. January is de performance
> month for me for the whole application.
>
> BUT the fact that a network EXE is slower then the local EXE
> can not be fixed by me, because this is a Microsoft Problem. I
> was hoping that someone could
> (a) confirm this problem with his application
> (b) give me a solution (registry etc)
> but I receive nothing about that.
>
> So, I also will have to write an application loader, and a new
> upgrade senario (this would be the most problem).
>
> Tx for your replies,
>
> Dirk
From: Marc Verkade [Marti IT] on
But then my measurements don't lie....

--
Grtz, Marc


"Geoff Schaller" <geoffx(a)softxwareobjectives.com.au> schreef in bericht
news:8mM1l.2352$cu.1053(a)news-server.bigpond.net.au...
> Actually the reverse should be true. A share is resolved at login whereas
> a UNC is re-evaluated on every use.
>
>
> "Marc Verkade [Marti IT]" <marcatM(a)rtidotnl> wrote in message
> news:49477e2b$0$765$58c7af7e(a)news.kabelfoon.nl:
>
>> Hai,
>>
>> We have seen that communicating through a share F:\App.exe works slower
>> than
>> using an UNC path like \\serverip\appshare\app.exe
>>
>> Perhaps worth a try.
>>
>> --
>> Grtz, Marc
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 3694 (20081215) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>

From: Geoff Schaller on
...and therefor some other factor is involved. Often it can be as simple
as the NIC being on auto select or even the hub on auto select. Put GB
cards in a LAN with 100MB cards and sometimes the same thing can happen.
Sometimes one workstation has Novell protocols enabled and others not.
There are a whole range of environmental factors that can affect this.
But in general, mapped drives should be the fastest access. There is
plenty of MS material to support this.

Geoff



"Marc Verkade [Marti IT]" <marcatM(a)rtidotnl> wrote in message
news:4947f982$0$793$58c7af7e(a)news.kabelfoon.nl:

> But then my measurements don't lie....
>
> --
> Grtz, Marc


__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3696 (20081216) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com