From: Massimo Bighelli on

Dirk

do you have a double antivirus ? (server+client) cheking database too ?


Massimo Bighelli
ARCA Sistemi S.r.l.




"Dirk (Belgium)" <dirk.dot.herijgers(a)pbprojects.dot.be> ha scritto nel
messaggio news:315%k.21167$aH5.9976(a)newsfe28.ams2...
> Geoff Schaller wrote:
>
>> Dirk,
>>
>> Any app that takes 9
>> seconds to open is in dire need of some work.
>>
>> Geoff
>>
>>
>>
>
>
> Geoff,
>
> This is what I want to say: The app is already loaded !!! 14 seconds is
> the time to open a specific childwindow, when EXE and DLL's are on
> network, but 9 seconds when EXE and DLL's are local (data is always
> network). Even opening this childwindow a second time, the difference
> in time still exist.
>
> Dirk
>
> --
>

From: Geoff Schaller on
Dirk,

Ok, then clearly the issue is the number of tables which are needed to
be opened for each tab (that is why we only ever build a tab on its
first show or select). The next problem is that subdatawindow and
databrowser are exceptionally slow when compared to bBrowser. A factor
of 10 times improvement is not out of the question.

I consider any window which takes 3 seconds to open as taking too long.
Our benchmark is subsecond.

Geoff



"Dirk (Belgium)" <dirk.dot.herijgers(a)pbprojects.dot.be> wrote in message
news:315%k.21167$aH5.9976(a)newsfe28.ams2:

> Geoff Schaller wrote:
>
>
> > Dirk,
> >
> > Any app that takes 9
> > seconds to open is in dire need of some work.
> >
> > Geoff
> >
> >
> >


__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3673 (20081208) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


From: Paul D B on
Dirk (Belgium) wrote:
> Geoff Schaller wrote:
>
>> Dirk,
>>
>> Any app that takes 9
>> seconds to open is in dire need of some work.
>>
>> Geoff
>>
>>
>>
>
>
> Geoff,
>
> This is what I want to say: The app is already loaded !!! 14 seconds
> is the time to open a specific childwindow, when EXE and DLL's are on
> network, but 9 seconds when EXE and DLL's are local (data is always
> network).

Is the "big" (and how big is it?) DLL loaded dynamically (with loadlibrary)
when you open the childwindow, or when you open the application? And what
about other DLL's (VO, bBrowser etc...) are they also located on the server
share?


>Even opening this childwindow a second time, the difference
> in time still exist.

If some DLL's are only loaded when you open that childwindow, they they will
be unloaded again if you close it (unless if they are being shared by
another application). If you subsequently reopen the childwindow, they will
be reloaded again.

Personally I think your problem is a DBF performance problem (because of
filtering maybe) and then it is easy to check: just put the DBF on the local
client instead of the server share: do you still need 9 seconds? Or it is a
GUI design problem. I have also made some very "heavy" windows with lots of
controls on lots of tabpages and I had to redesign them because performance
was awful.

--
Paul


From: Dirk (Belgium) on
Massimo Bighelli wrote:

>
> Dirk
>
> do you have a double antivirus ? (server+client) cheking database too
> ?
>
>
> Massimo Bighelli
> ARCA Sistemi S.r.l.
>
>
>
>

Hi,

No antivirus at all !!!

Dirk

--

From: Dirk (Belgium) on
Geoff Schaller wrote:

> Dirk,
>
> Ok, then clearly the issue is the number of tables which are needed
> to be opened for each tab (that is why we only ever build a tab on
> its first show or select). The next problem is that subdatawindow and
> databrowser are exceptionally slow when compared to bBrowser. A
> factor of 10 times improvement is not out of the question.
>
> I consider any window which takes 3 seconds to open as taking too
> long. Our benchmark is subsecond.
>
> Geoff
>
>
>

Geoff,

You still not understand it. The databases are in both situations
located at the server.

I agree with you that 9 seconds are too long, BUT WHY is there a
difference in time, between a local EXE and a network EXE ?

Dirk

--