Kbase 13829: Multitasking-interval and Process events CPU time MS-Windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/19/1999 |
|
Multitasking-interval and Process events CPU time MS-Windows
In order to allow other MS-Windows tasks to have some CPU
time, you must adjust the MULTITASKING-INTERVAL in the
Progress.ini file. This value is used to adjust how
co-operative PROGRESS is in the MS_Windows environment. If
it is set to 0 then Progress will "hog" CPU time and run
very fast. A higher number will allow more multi-tasking.
If you are doing a long processing loop such as:
DEF VAR i AS INT.
DO i = 1 TO 1000:
<calculate something>.
END.
The PROGRESS V7 session will hog the CPU under Windows for
that entire time. There are many work arounds to this:
1. Set MULTITASKING-INTERVAL to something other than 0 in
the PROGRESS.INI file. (50 is a good number).
2. Set SESSION:MULTITASKING-INTERVAL to something other
than 0 in the 4GL code.
3. Run the long processing loop in
batch mode
4. Pepper the long processing loop with PROCESS
EVENTS statements.
Progress Software Technical Support Note # 13829