> 3) Calls like FreeMem, CompactMem, etc don't seem to work correctly in
> OS X, or have no effect in OS X. Am I right in assuming that these
> calls are essentially meaningless in OS X? How do I assess how much I
> really have? I can't use grow zone procs to let me know I am getting
> tight.
Yes. And under OS X handles never move (except when you resize them to be
bigger). In fact handles are useless except to pass to old-fashioned APIs
that use them. The idea of course is that you just use malloc/free or
new/delete and let the VM manager handle things. Of course, in your case you
seem to be overloading the VM manager.
I can only think of 2 ways to address this:
- restructure the application to have a database at the backend and cache
the MRU portion of the db in some amount of RAM that won't choke the system
(512MB is definitely doable from my own experiments, I bet you could get
away with 1GB).
- require Tiger; make your computation engine a 64-bit process.
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 665-7007 voice
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
