[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Identifying sources of allocations in a toy Mandelbrot package
From: |
Emanuel Berg |
Subject: |
Re: Identifying sources of allocations in a toy Mandelbrot package |
Date: |
Wed, 17 Jan 2024 14:25:25 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Psionic K wrote:
> All that was fun, but what I don't understand is where this
> package manages to consume up to 7GB of memory, which Emacs
> will not readily give back afterwards.
You have a pretty big vector
(* 1600 1200 3) ; 5 760 000
and a lot of nested iteration
(* 1200 1600 256) ; 491 520 000
Maybe you can even compute further how big it should get
without GC?
--
underground experts united
https://dataswamp.org/~incal
- Identifying sources of allocations in a toy Mandelbrot package, Psionic K, 2024/01/17
- Re: Identifying sources of allocations in a toy Mandelbrot package, Psionic K, 2024/01/19
- Re: Identifying sources of allocations in a toy Mandelbrot package, Tomas Hlavaty, 2024/01/19
- Re: Identifying sources of allocations in a toy Mandelbrot package, Psionic K, 2024/01/19
- Re: Identifying sources of allocations in a toy Mandelbrot package, Psionic K, 2024/01/19
- Re: Identifying sources of allocations in a toy Mandelbrot package, Eli Zaretskii, 2024/01/20
- Re: Identifying sources of allocations in a toy Mandelbrot package, Tomas Hlavaty, 2024/01/20
- Re: Identifying sources of allocations in a toy Mandelbrot package, Psionic K, 2024/01/20
- Re: Identifying sources of allocations in a toy Mandelbrot package, Eli Zaretskii, 2024/01/20
- Re: Identifying sources of allocations in a toy Mandelbrot package, Tomas Hlavaty, 2024/01/26
- Re: Identifying sources of allocations in a toy Mandelbrot package, Psionic K, 2024/01/26