Re: Gradual Growth of Memory Use?

"David McClain (as dbm at refined-audiometrics dot com)" <[email protected]>
Newsgroups gmane.lisp.lispworks.general
Message-ID <[email protected]>
I just did a (GC-GENERATION 3), about half-hour after the last dump. Here is the new dump: (Now shows 460,000 Actors, up from 342,000 !!??)

(#S(CLASS-COUNTER :NAME CONS
                  :COUNT 8821834
                  :TOTAL-SIZE 141149344
                  :CUMULATIVE-SIZE 324811016)
 #S(CLASS-COUNTER :NAME FUNCTION
                  :COUNT 1456012
                  :TOTAL-SIZE 71371256
                  :CUMULATIVE-SIZE 183661672)
 #S(CLASS-COUNTER :NAME SIMPLE-VECTOR
                  :COUNT 2221920
                  :TOTAL-SIZE 69226000
                  :CUMULATIVE-SIZE 112290416)
 #S(CLASS-COUNTER :NAME COM.RAL.ACTORS:ACTOR
                  :COUNT 459690
                  :TOTAL-SIZE 11032560
                  :CUMULATIVE-SIZE 43064416)
 #S(CLASS-COUNTER :NAME CLOS::SYSTEM-OBJECT
                  :COUNT 127772
                  :TOTAL-SIZE 7416080
                  :CUMULATIVE-SIZE 32031856)
 #S(CLASS-COUNTER :NAME VECTOR
                  :COUNT 3110
                  :TOTAL-SIZE 5701968
                  :CUMULATIVE-SIZE 24615776)
 #S(CLASS-COUNTER :NAME SIMPLE-STRING
                  :COUNT 22319
                  :TOTAL-SIZE 5269464
                  :CUMULATIVE-SIZE 18913808)
 #S(CLASS-COUNTER :NAME SYMBOL
                  :COUNT 103353
                  :TOTAL-SIZE 4960944
                  :CUMULATIVE-SIZE 13644344)
 #S(CLASS-COUNTER :NAME SIMPLE-BASE-STRING
                  :COUNT 126192
                  :TOTAL-SIZE 3817624
                  :CUMULATIVE-SIZE 8683400)
 #S(CLASS-COUNTER :NAME DOUBLE-FLOAT
                  :COUNT 27586
                  :TOTAL-SIZE 441376
                  :CUMULATIVE-SIZE 4865776)


> On Mar 19, 2025, at 06:43, David McClain (as dbm at refined-audiometrics dot com) <[email protected]> wrote:
> 
> 
> 
>> On Mar 19, 2025, at 06:02, Martin Simmons <[email protected]> wrote:
>> 
>> I suggest comparing those counters with another call to size-by-class/loop
>> when the image has grown some more.  After that, you could do (gc-generation
>> 3) and compare again to see if the objects were really live or just stuck in
>> generation 3.
> 
> 
> So, from your suggestion, it would make most sense to perform (gc-generation 3) before doing the memory dump from Tim? Allow the system to discard the accumulated garbage first? Then compare dumps from two separated times.
> 
> My experience running (gc-generation 3) in the past has shown that the memory image is indeed increasing. The results of the call do keep increasing, which would indicate memory actually in-use.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.