MD>Should you just pick a goodly large number (say, 100Meg) leaving the
MD>memory uncommitted till you need it, then grow the suballoced heap? 
MD>Should you take the 512Meg that your application is limited to?  Or
MD>should you pick a smaller amount to allocate, based on calculations
MD>that I don't know about?  

Pick a large number.. 512M is a nice round number..


MD>   Do you handle memory differently depending on the application? 
MD>For instance, one of my applications will have sets of linked lists
MD>(the length of which I don't know) where memory will be allocated in
MD>lots of tiny chunks. Another application will have large bitmapped
MD>images, eating up 200k+ chunks each.  Is it better to use
MD>suballocated memory in one case and plain old nonshared memory in
MD>another?

suballocated memory can be shared or non shared. What was your question
again...

___
 * MR/2 2.1 NR * Jesus loves you.  Everyone else thinks you're a jerk!

--- QScan v1.067b