Database Search
TechHome
 | |
|
- 10130 BoxesUP Invalid Rect String
- 16 versus 32 bit EXEs
- 3088 or 1591 - FileRead - Attempt to Read Past EOF
- All Compiled Exes Start to Crash
- Code Sign Error
- Compile Error 1125 FileTimeGet File Not Found
- Compiled EXE Size Compared to WBT
- Compiled vs Studio and Includes with UDFs
- Compiler 1126 BinaryAlloc Error
- Compiler Error 1337 Dialog Box Creation Error
- Compiler Explained
- Compiler Hangs
- Compiler Not Remembering Previous Settings
- Compiler Removes Remarks
- Compiler Runtime Error - EXE File Open Failed
- Compiler Source File Limit
- Compiler Splash Screen Explained
- Compiler Version Information Field Limit
- Compiler Versions with Compression
- Decompile a Compiled WB EXE
- Determine Version of Compiler Used to Compile an EXE
- Distinguish between WBTs and WBCs
- Does it Run Faster or Use More Resources
- Encode Error - Input File Too Big
- Encode for Calls from EXE files
- Encryped Encoded Verification Failed
- Encrypted Encoded Error
- Exe Crack Protection
- EXE Wont Launch on other PCs
- Extenders not Showing up in Compiler List
- Extract Files on Removeable Drive
- Extract WIL DLL To Specified Directory
- ExtractAttachedFile only Newer Files
- Firefox Problem Downloading Compiler ZIP
- How to Embed Source Code
- Icon Formatting Tools
- Icons and Compiler 2002
- Icons and the Compiler (old versions)
- Icons
- Include Shortcut as Other File in Compile
- Include Statements - How They Work
- Large versus Small EXE Model
- Missing msfvw32 dll
- Newer WBCs called from Older EXE
- Other Files Check Before Overwrite
- Other Files Explained
- Output File Open Failed
- Saved Compiler Settings
- Using WBC Files
- WB EXE is in Use by Another Program Error
- What Encryption is Used
- Win32 Network Extenders and Compiler
- Work Buffer Error when Compiling
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
WinBatch Running Slowly.
Does Compiler Use More System Resources?
Keywords: speed WinBatch Runs slowly. Is Compiler faster?
Why is it that the compiled version of a program seems to take up more resources than the wbt version. I wrote a short program that consists mainly of sendkey commands to automate repetitive entries in an application. The wbt version works fine, yet when I run the compiled exe version, the applications' windows can't keep up with the send key commands. When a new window is brought up it seems much slower coming up/painting. I ended up having to add delays of a few seconds between each send key that involved new windows in order for the compiled version of the program to work properly on my poor overworked 486 dx266. Any comments or tricks you can offer?
Answer:
The compiled and interpreted versions should run *identically*.The compiled version (especially if you use the BIG exe model) takes a small tad more memory, but not usually enought to affect anything. If you are suffering with a 4MB Ram system you *might* see some speed differences.
The usual problem is that the interpreter and compiler are out of sync with each other. Make sure you're using the same versions of both WinBatch and Compiler.
On the speed issue: A 100Mhz Pentium should process more than 500 simple statements a second. For batch file processing sorts of stuff, this is very reasonable; for complex number crunching it is clearly not acceptable.
Try this:
a=0
a1=GetExactTime()
for x=1 to 1000
a=a+1
next
a2=GetExactTime()
Message(a1,a2)
On a 486/33 mHZ laptop this takes 14 seconds. It executes about 3000 statements, for 215 statements a second. Try it on yours to see what kind of number you get. If it is 'very slow' there could be some kind of configuration problem.
Another thing to check is what other windows apps are running and at what priority. For example, a MS-DOS window running with a high priority, will greatly slow down all Windows processing.
Article ID: W12783
Filename: Does it Run Faster or Use More Resources.txt
File Created: 1999:04:15:16:49:36
Last Updated: 1999:04:15:16:49:36