Performance over network
in [Visual Objects]
|
Prev: Vulcan Advantages (was Choice SQL Database)
Next: mySQL_msSQL_Oracle connection and other relations / ALL command
From: Dirk (Belgium) on 5 Dec 2008 10:18 Hi All, Does someone has an explication for the following : I have a application with a small EXE and big DLL's written in VO. All data (DBF) are located on a server (XP Professional). Inside this programm, I have a big childwindow with several tabs a subdatawindows en subdatabrowsers... When opening this big childwindow, it takes about 14 seconds before the window is opened. When I place the EXE and DLL on the local machine, but the data still stay on the network, the big childwindow takes about 9 seconds for opening !!! I does not expect that the place of the exe take such a long time (!). The time measured is only the time to open this window, not the time to open the program, so EXE and DLL's are already fully loaded... Can someone give me an explanation, or some reason, or links to the internet with the same performance issue ??? Thanks for all your replies, Dirk (Belgium) --
From: Alessandro Antonangeli on 5 Dec 2008 10:48 There may be a lot of causes The firsts than comes to my mind are there are some SetFilter: they are terribly slow over a network and DBF has a lot of records you use a lot of objects and you go near the limit of memory of the program: try increasing the moemory available to the program try using the dbf locally also to see if this may be the problem -- Ciao Alessandro "Dirk (Belgium)" <dirk.dot.herijgers(a)pbprojects.dot.be> ha scritto nel messaggio news:DDb_k.1172$Ne1.225(a)newsfe21.ams2... > Hi All, > > Does someone has an explication for the following : > > I have a application with a small EXE and big DLL's written in VO. > > All data (DBF) are located on a server (XP Professional). > > Inside this programm, I have a big childwindow with several tabs a > subdatawindows en subdatabrowsers... > > When opening this big childwindow, it takes about 14 seconds before the > window is opened. > > When I place the EXE and DLL on the local machine, but the data still > stay on the network, the big childwindow takes about 9 seconds for > opening !!! > > I does not expect that the place of the exe take such a long time (!). > The time measured is only the time to open this window, not the time to > open the program, so EXE and DLL's are already fully loaded... > > Can someone give me an explanation, or some reason, or links to the > internet with the same performance issue ??? > > > Thanks for all your replies, > > Dirk (Belgium) > > --
From: Dirk (Belgium) on 5 Dec 2008 11:29 Alessandro Antonangeli wrote: > There may be a lot of causes > The firsts than comes to my mind are > there are some SetFilter: they are terribly slow over a network and > DBF has a lot of records you use a lot of objects and you go near the > limit of memory of the program: try increasing the moemory available > to the program try using the dbf locally also to see if this may be > the problem Hi Alessandro, I think you don't understand the problem (or I have not explain it well) In both cases; the data is placed on a share on a server But, in first case, the EXE and DLL are local: Then it takes 9 secondes And, in second case, the EXE and DLL are on the network: It takes 14 secondes. I believe it can nothing have to do with the way you access your data. It must have to do something how Microsoft handles reading "EXE's" and "DLL's" over a network... Dirk --
From: Jamal on 5 Dec 2008 13:03 When you run an application across the nework directly, resources of the EXE get downloaded across the network cables then it runs, that's why it's slower. The alternative is Terminal Services which is designed for this purpose. Jamal "Dirk (Belgium)" <dirk.dot.herijgers(a)pbprojects.dot.be> wrote in message news:KFc_k.16188$uy1.3675(a)newsfe23.ams2... > Alessandro Antonangeli wrote: > >> There may be a lot of causes >> The firsts than comes to my mind are >> there are some SetFilter: they are terribly slow over a network and >> DBF has a lot of records you use a lot of objects and you go near the >> limit of memory of the program: try increasing the moemory available >> to the program try using the dbf locally also to see if this may be >> the problem > > Hi Alessandro, > > I think you don't understand the problem (or I have not explain it well) > > In both cases; the data is placed on a share on a server > But, in first case, the EXE and DLL are local: Then it takes 9 secondes > And, in second case, the EXE and DLL are on the network: It takes 14 > secondes. > > I believe it can nothing have to do with the way you access your data. > It must have to do something how Microsoft handles reading "EXE's" and > "DLL's" over a network... > > Dirk > > -- >
From: Alessandro Antonangeli on 6 Dec 2008 06:24
> > Hi Alessandro, > > I think you don't understand the problem (or I have not explain it well) > > In both cases; the data is placed on a share on a server > But, in first case, the EXE and DLL are local: Then it takes 9 secondes > And, in second case, the EXE and DLL are on the network: It takes 14 > secondes. I thougt you were complaining about also of the 9 seconds to open the windows. If it is only about the different time of loading, it depend on how much slow is your lan (apparentely a lot <g>) As far as I know, DLL are not full loaded at start up: at startup there is only a check for the existance and for what functions that are inside. When the program need to call a function it load it in memory. So if it is a big dll, it make take time (even if 5 more second are a lot of time) trought the network. Because it take so much time to load even in local, I suspect a memory problem (9 seconds are so much time!). I would try this lines (or higher value) as the first thing in your app:start DynSize(160) SetMaxDynSize(67108864) -- Ciao Alessandro |