Performance over network
in [Visual Objects]
|
Prev: Vulcan Advantages (was Choice SQL Database)
Next: mySQL_msSQL_Oracle connection and other relations / ALL command
From: Massimo Bighelli on 9 Dec 2008 07:16 Dirk, then you have some strange network behavior BUT even if I agree with Geoff, I aunderstand database is not the problem and I know that exe+dll over net may be quite slow. This is one of the reasons -IMO- to put exe and dll on the workstations. Some problem to solve, ie serverInstall is different from workstationInstall, autoupdate, and so on, but a lot of advantages too. Massimo Bighelli ARCA Sistemi S.r.l. "Dirk (Belgium)" <dirk.dot.herijgers(a)pbprojects.dot.be> ha scritto nel messaggio news:I3r%k.9765$So1.1410(a)newsfe01.ams2... > 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: Malcolm on 9 Dec 2008 07:09 > 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 ? In the past I have heard it described as a difference in the paging algorithm - a local DLL can be paged in from disk when required, a network dll may be copied locally first as it does not trust it continuing to exist/fears the latency will be too long.
From: Paul D B on 9 Dec 2008 08:06 Dirk (Belgium) wrote: > 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 Dirk, if you don't answer our questions then don't expect us to say something sensible. - You said small EXE and big DLL. What does that mean? Some figures please. - Do you use Loadlibrary or are the DLL's linked in? - When you open the problematic childwindow, do you load additional DLL's? - What network speed and what CPU on the client? - What network speed on the server? (Since I have a very fast PC and a Gigabit network all my VO apps on the server launch instantly; before it took ages. Exactly the same applications, same data! ) PS: Even the smallest VO-app will need 25-30 MB of memory to load; that is your EXE and the VO-runtime. Over a slow network, that means something. -- Paul
From: Amilcar A. Camargo on 9 Dec 2008 13:30 Hi Dirk, On Tue, 09 Dec 2008 09:43:45 GMT, "Dirk (Belgium)" <dirk.dot.herijgers(a)pbprojects.dot.be> wrote: >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 ? Your app working directory: is defined on the server? If so, any file open or search that windows needs o perform will scan first your network directory and then those defined on PATH statement. That should add to your access time always. HTH, Amilcar A. Camargo F. Guatemala, C. A.
From: Dirk (Belgium) on 10 Dec 2008 04:00
Paul and others The size of EXE is 2,5 MB There are 19 DLL's , together for about 50 MB EXE's and DLL are on the network. If I create one big EXE with no DLL's, the problem is the same. DLL's are loaded with loadlibrary() on the start of the program, so before opening the childwindow. The speed of 9 seconds with local EXE and 14 seconds for network EXE is the mean of 5 times opening this childwindow. The first opening of the childwindow is about 2 seconds slower, what I can understand. The following openings have all the same time. DBF's are always on the network. 'Searching' for files is not done, because I always gives a path. It can not be the 'data', because this data is always accessed in the same way (i.e. network!). A network monitor shows me that there is traffic on the network, but that is normal and logical. Solution: I am thinking about a App-loader, for copying the EXE and DLL's from network to local. But I want to create a dynamic app-loader. Has someone an example for this ? Dirk -- |