even saving a record to a .dbf file(119 fields) takes 1 second on the server, the 'same' takes 14 seconds from any client/terminal.
Il 27/01/2023 12:03, timepro timesheet ha scritto:emg:
even saving a record to a .dbf file(119 fields) takes 1 second on the server, the 'same' takes 14 seconds from any client/terminal.It is not normal. You need to check your code and/or your network hardware.
--
Enrico Maria Giordano
http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg
emg:
seems the bottleneck is in my system design.
the time consuming/slow process happens at more than 30+ diff. locations where my app is installed.
-is my client-server mapping procedure proper/standard.
-could it be an issue with 'set default to...'
-what is YOUR client/server setup. do you install your .exe file in each client/system. (besides the server)
-from each of your client/terminal, how do you access,open,update,process... data/files residing in the server
Il 27/01/2023 13:12, timepro timesheet ha scritto:
emg:
seems the bottleneck is in my system design.
the time consuming/slow process happens at more than 30+ diff. locations where my app is installed.
-is my client-server mapping procedure proper/standard.I don't know.
-could it be an issue with 'set default to...'Not that I'm aware of.
-what is YOUR client/server setup. do you install your .exe file in each client/system. (besides the server)I install everything in the server disk (EXE, DBF, etc.). The clients
have only a desktop link to the shared EXE.
-from each of your client/terminal, how do you access,open,update,process... data/files residing in the serverNothing special. I only pay attention to properly lock records, but this cannot slow down the DBF access.
--
Enrico Maria Giordano
http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg
emg, would you please:
(in your client/server setup)
-with your 'shared' .exe, do you store/save ALL your .dbf files in the server ONLY - no matter which client/system inputs/accesses the .dbf.
-inside your .prgs, do you use 'set relation to' to open/use .dbf files
-do you map only the folder your app. resides in -or- the full drive of the server where your app's folder is resident.
Il 31/01/2023 11:29, timepro timesheet ha scritto:thanks emg:
emg, would you please:
(in your client/server setup)Yes.
-with your 'shared' .exe, do you store/save ALL your .dbf files in the server ONLY - no matter which client/system inputs/accesses the .dbf.
-inside your .prgs, do you use 'set relation to' to open/use .dbf filesI usually use SET SCOPE but SET RELATION is also fine. You have to
isolate the code that causes the slow down. There is no other way to understand the problem.
-do you map only the folder your app. resides in -or- the full drive of the server where your app's folder is resident.It is irrelevant.
--
Enrico Maria Giordano
http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg
You have to isolate the code that causes the slow down...
that's exactly what/where i can't figure out.
reckon, will read each line of my prgs & visualise the outcome...
(it could be very elementary if i isolate it/stumble upon.)
emg, may i get a sample of your app's icon properties (app icon on the client/terminal)
(target & startin)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 251 |
Nodes: | 16 (0 / 16) |
Uptime: | 03:29:50 |
Calls: | 5,571 |
Files: | 11,686 |
Messages: | 5,131,680 |