On 10/5/2012 3:36 PM, Richard Kaye wrote:
Not if the SYS function you're using to determine the bounds is blowing up
because it can't understand what is being returned.
The point I was trying to get to was even if it can "see" up to 3GB or 4GB, it
doesn't use it in an efficient way. That was the gist of what I had read; once you go
over a certain allocation there's no discernible performance improvement to be had. So
just cap it at 480MB or 512MB and leave the rest to the OS.
Of course, as TR would say, you need to test in your environment with realistic
data sets before determining what the optimal SYS(3050) setting is. Or maybe
Christof will pop in and give us the definitive answer... :-)
Yeah, I'd heard the same thing. And the part about the ABS() I get now
too. Without it, it was trying to use a negative value and of course
that's nonsense.
Cool thread. Thanks all for chiming in.
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
http://fabmate.com
http://twitter.com/mbabcock16
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
