Using SYS(3050)

One of our customers has suggested using SYS(3050) to limit the memory use of
VFP (they suggest 512Mb) when packing large tables (2Gb). They suggest this
is only nessecary on Windows 2003 server standard editon

I am reluctant to impliment this for all our customers as i was under the
impression that VFP was the best memory manager.

Does anybody have any tips regarding this

thanks
greg

Fred
Mon Feb 14 23:34:35 CST 2005

ftp://leafe.com/setmemory.zip

You might also find other useful items at http://leafe.com/dls/vfp
--
Fred
Microsoft Visual FoxPro MVP


"Greg" <Greg@discussions.microsoft.com> wrote in message
news:E9859B88-F085-4F56-A0BD-0F537A671E36@microsoft.com...
> One of our customers has suggested using SYS(3050) to limit the memory use
> of
> VFP (they suggest 512Mb) when packing large tables (2Gb). They suggest
> this
> is only nessecary on Windows 2003 server standard editon
>
> I am reluctant to impliment this for all our customers as i was under the
> impression that VFP was the best memory manager.
>
> Does anybody have any tips regarding this
>
> thanks
> greg

Greg
Tue Feb 15 03:31:01 CST 2005

Thanks Fred
Any idea if its a problem setting vfp sys(3050) to above the
DECLARE GlobalMemoryStatus IN Win32API returned value?

Greg

"Fred Taylor" wrote:

> ftp://leafe.com/setmemory.zip
>
> You might also find other useful items at http://leafe.com/dls/vfp
> --
> Fred
> Microsoft Visual FoxPro MVP
>
>
> "Greg" <Greg@discussions.microsoft.com> wrote in message
> news:E9859B88-F085-4F56-A0BD-0F537A671E36@microsoft.com...
> > One of our customers has suggested using SYS(3050) to limit the memory use
> > of
> > VFP (they suggest 512Mb) when packing large tables (2Gb). They suggest
> > this
> > is only nessecary on Windows 2003 server standard editon
> >
> > I am reluctant to impliment this for all our customers as i was under the
> > impression that VFP was the best memory manager.
> >
> > Does anybody have any tips regarding this
> >
> > thanks
> > greg
>
>
>

Fred
Tue Feb 15 09:07:51 CST 2005

If you set your memory too large, you'll cause VFP to use the SWAP file.
It's all the same to VFP except for the speed.

--
Fred
Microsoft Visual FoxPro MVP


"Greg" <Greg@discussions.microsoft.com> wrote in message
news:911F4881-853B-476C-A399-047A14429FDA@microsoft.com...
> Thanks Fred
> Any idea if its a problem setting vfp sys(3050) to above the
> DECLARE GlobalMemoryStatus IN Win32API returned value?
>
> Greg
>
> "Fred Taylor" wrote:
>
>> ftp://leafe.com/setmemory.zip
>>
>> You might also find other useful items at http://leafe.com/dls/vfp
>> --
>> Fred
>> Microsoft Visual FoxPro MVP
>>
>>
>> "Greg" <Greg@discussions.microsoft.com> wrote in message
>> news:E9859B88-F085-4F56-A0BD-0F537A671E36@microsoft.com...
>> > One of our customers has suggested using SYS(3050) to limit the memory
>> > use
>> > of
>> > VFP (they suggest 512Mb) when packing large tables (2Gb). They suggest
>> > this
>> > is only nessecary on Windows 2003 server standard editon
>> >
>> > I am reluctant to impliment this for all our customers as i was under
>> > the
>> > impression that VFP was the best memory manager.
>> >
>> > Does anybody have any tips regarding this
>> >
>> > thanks
>> > greg
>>
>>
>>

Cyrus
Tue Feb 15 10:04:18 CST 2005

Fred Taylor wrote:
> If you set your memory too large, you'll cause VFP to use the SWAP file.
> It's all the same to VFP except for the speed.
>
Thats the problem that VFP has, it can't tell if the memory it's using
is swap file or real memory. Playing with SYS(3050) can increase
performance.

--
Cy Welch
Senior Programmer
MetSYS Inc
http://www.metsysinc.com

Anders
Tue Feb 15 09:39:45 CST 2005

Published testing suggests much lower limits. SYS(3050,1, 8 to 16 MB), same
for SYS(3050,2) .
-Anders

"Greg" <Greg@discussions.microsoft.com> wrote in message
news:E9859B88-F085-4F56-A0BD-0F537A671E36@microsoft.com...
> One of our customers has suggested using SYS(3050) to limit the memory use
of
> VFP (they suggest 512Mb) when packing large tables (2Gb). They suggest
this
> is only nessecary on Windows 2003 server standard editon
>
> I am reluctant to impliment this for all our customers as i was under the
> impression that VFP was the best memory manager.
>
> Does anybody have any tips regarding this
>
> thanks
> greg

Gene
Mon Feb 21 13:28:45 CST 2005

Anders Altberg wrote:
> Published testing suggests much lower limits. SYS(3050,1, 8 to 16 MB), same
> for SYS(3050,2) .
> -Anders

I would be intrested in these test results, do you have a link ?

>
> "Greg" <Greg@discussions.microsoft.com> wrote in message
> news:E9859B88-F085-4F56-A0BD-0F537A671E36@microsoft.com...
>
>>One of our customers has suggested using SYS(3050) to limit the memory use
>
> of
>
>>VFP (they suggest 512Mb) when packing large tables (2Gb). They suggest
>
> this
>
>>is only nessecary on Windows 2003 server standard editon
>>
>>I am reluctant to impliment this for all our customers as i was under the
>>impression that VFP was the best memory manager.
>>
>>Does anybody have any tips regarding this
>>
>>thanks
>>greg
>
>

Anders
Tue Feb 22 11:35:28 CST 2005

Do a Google for "SYS(3050"
You'll find a discussion on the Wiki forum about memory using Citrix TS
where Steven Black thinks 60MB is optimal while Peter Stordiau says 8MB per
user is best.
Les Pinter sets 15MB generally in an article about using Westwind
-Anders

"Gene Vital" <nothankyou@msnew.com> wrote in message
news:OkJFRuEGFHA.3928@TK2MSFTNGP09.phx.gbl...
> Anders Altberg wrote:
> > Published testing suggests much lower limits. SYS(3050,1, 8 to 16 MB),
same
> > for SYS(3050,2) .
> > -Anders
>
> I would be intrested in these test results, do you have a link ?
>
> >
> > "Greg" <Greg@discussions.microsoft.com> wrote in message
> > news:E9859B88-F085-4F56-A0BD-0F537A671E36@microsoft.com...
> >
> >>One of our customers has suggested using SYS(3050) to limit the memory
use
> >
> > of
> >
> >>VFP (they suggest 512Mb) when packing large tables (2Gb). They suggest
> >
> > this
> >
> >>is only nessecary on Windows 2003 server standard editon
> >>
> >>I am reluctant to impliment this for all our customers as i was under
the
> >>impression that VFP was the best memory manager.
> >>
> >>Does anybody have any tips regarding this
> >>
> >>thanks
> >>greg
> >
> >

Thomas
Tue Feb 22 12:20:45 CST 2005

Anders Altberg schrieb:
> Do a Google for "SYS(3050"
> You'll find a discussion on the Wiki forum about memory using Citrix TS
> where Steven Black thinks 60MB is optimal while Peter Stordiau says 8MB per
> user is best.
> Les Pinter sets 15MB generally in an article about using Westwind
You have to put this in context of the application running and the
machine it is running on. For instance a single user app doing heavy
data crunching in SQL or using Rushmore often will be better off if
sys(3050) is near the free physical memory, *especially* if running
under OS<W2K.

Looking up "previous research" might give you false leads because
machines and caching strategies change quite a bit.
You should always try to verify the found results on your current
platform as well as trying to build a testcase for your specific scenario.

My rule of thumb under W2K and XP for single (power-)usermode is
33-45% of free physical memory on well equipped (>512MB) machines.
For multiuser apps lower the amount, especially in writeheavy apps.

On memory poor systems (<192MB) check the probability of
other programs gobbling up more memory as well as stremlining
the loaded tasks<g>.

If you *don't* use rushmore and have very straight, old xbase
using seek(), scan rest you can set sys(3050) to much lower levels
while keeping the speed. But that kind of coding isn't needed usually...


my 0.02 EUR

thomas