running start-gc-monitor

Hi All,
      I've hit a crucial memory limit in a Mac Mini Server,  which  
does not affect a 2008 XServe.  Both are running MacOSX Lion,  and the  
Mac Mini has 16 GB (3rd party memory),  whereas the XServe has 32 GB,   
a standard configuration for the XServe.

     When Lispworks loads about 6 GB into a tree of hash tables, the  
Mac Mini cannot seem to give more than 5.2 GB virtual memory to  
Lispworks,  which then goes into what looks like an endless gc thrash.

     Yet when Lispworks loads about 6 GB into a tree of hash tables,  
the Xserve allocates 9.5 GB virtual memory to Lispworks,  which  
quickly gc's that back to 7 GB to successfully complete the hash table  
load.

    I suspect that the Mac Mini, which Apple only supports in  
configurations up to 8GB,  is somehow withholding memory from  
Lispworks beyond 5.2 GB. I'd like to run start-gc-monitor, to see  
better what's going on in the Mac Mini,  but this command does not work:

(capi:start-gc-monitor (capi:convert-to-screen))

Error: No applicable methods for #<STANDARD-GENERIC-FUNCTION CAPI- 
LIBRARY:SCREEN-REPRESENTATION-START-GC-MONITOR 411071D51C> with args  
(#<CAPI-COCOA-LIBRARY::SCREEN-REPRESENTATION for #<CAPI:COLOR-SCREEN 0  
Cocoa> 42402EFE53>)
   1 (continue) Call #<STANDARD-GENERIC-FUNCTION CAPI-LIBRARY:SCREEN- 
REPRESENTATION-START-GC-MONITOR 411071D51C> again
   2 (abort) Return to level 0.
   3 Return to top loop level 0.

Type :b for backtrace or :c <option number> to proceed.
Type :bug-form "<subject>" for a bug report template or :? for other  
options.


Could someone show me how to run start-gc-monitor, from the Listener?

Lawrence Au

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html