Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Size of a VFP automation server
Message
De
04/05/1999 11:48:35
 
 
À
04/05/1999 09:20:58
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00214762
Message ID:
00214998
Vues:
20
>I think you misread the number: It is not 1600, but grows to more than 16000 KB (16 meg) and keeps growing as I hit on it.
>My feeling is that the problem lies with either:
>- the version of foxisapi.dll i am using.
>- using the correct configuration (multi use vs. single use) for the ole server classes.
>- keeping the same data environment open (tables and databases) at all times when the process myapp.exe is still alive in memory.
>

No, this is a VFP behavior - if it can glom memory, it does, unless you put limits on its appetite for buffer space. SYS(3050) can limit this, and allows you to set distinct values for foreground and background operation. I'd make plans to let it allocate at least a couple of meg per instance in the background, and more than that in the foreground; something like:

=SYS(3050,1,4000000) && 4 meg of buffer space in foreground
=SYS(3050,2,2000000) && 2 meg in background

VFP will allocate maybe an addition 1MB for things other than buffer and workspace. I'd increase the values if only one instance is going to be running at any time and you can spare the space, but I probably wouldn't use a value larger than the physical memory installed in the system.

>but I am not sure. help.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform