Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Memory Management
- Thread starter teknik
- Start date
darrellblackhawk
Programmer
teknik:
There are a number of factors that affect application performance. Typically, an exe is going to be faster than an associated app or prg.
I'd first have to ask; what are you doing in the app?
It's hard to tell what could be slowing down your app without a little more information.
A couple of questions:
Is the app, after compiling, running on a different machine than it was developed on?
If so, the obvious question is; what are the differences between the target machine(running the exe) and the development machine?
Darrell
There are a number of factors that affect application performance. Typically, an exe is going to be faster than an associated app or prg.
I'd first have to ask; what are you doing in the app?
It's hard to tell what could be slowing down your app without a little more information.
A couple of questions:
Is the app, after compiling, running on a different machine than it was developed on?
If so, the obvious question is; what are the differences between the target machine(running the exe) and the development machine?
Darrell
Mike Gagnon
Programmer
Teknik
The coverage Profiler application might be the tool to use in your case, and try to pinpoint where your application bogs down. You can access from Tools->Coverage Profiler:
A coverage application writes information about which lines of code in a file were run. A profiler application provides information about which lines actually run, how many times a line is run, duration, and more. Coverage and profiling enable a developer to identify problem areas in an application, especially skipped code and performance bottlenecks.
Mike Gagnon
The coverage Profiler application might be the tool to use in your case, and try to pinpoint where your application bogs down. You can access from Tools->Coverage Profiler:
A coverage application writes information about which lines of code in a file were run. A profiler application provides information about which lines actually run, how many times a line is run, duration, and more. Coverage and profiling enable a developer to identify problem areas in an application, especially skipped code and performance bottlenecks.
Mike Gagnon
![[pc2]](/data/assets/smilies/pc2.gif "[pc2] [pc2]")
Teknik,
While the coverage profiler will tell you where you are spending your time and what code to optimize, I've found that there are other things to check. A starting list:
1) Available memory on workstation when running. Depending on it's OS and what else is running, a "large" app VFP could require 128 - 512 MB.
2) Location of temp files - these should ALWAYS be on the local system, not on the network. Lots of free space and a regularly defragged system can make a huge difference.
3) Network traffic / stability - Bad NICS, hubs, switches, routers, cables can cause a lot of retries that can cripple a database application.
4) Missing or wrong indexes on the data files - too many can really slow down updates, and not enough will restrict optimization possibilities.
Rick
While the coverage profiler will tell you where you are spending your time and what code to optimize, I've found that there are other things to check. A starting list:
1) Available memory on workstation when running. Depending on it's OS and what else is running, a "large" app VFP could require 128 - 512 MB.
2) Location of temp files - these should ALWAYS be on the local system, not on the network. Lots of free space and a regularly defragged system can make a huge difference.
3) Network traffic / stability - Bad NICS, hubs, switches, routers, cables can cause a lot of retries that can cripple a database application.
4) Missing or wrong indexes on the data files - too many can really slow down updates, and not enough will restrict optimization possibilities.
Rick
- Status
Similar threads
- Locked
- Question
