![](https://secure.gravatar.com/avatar/d360ec751eb90bc963c5b03544d88cf5.jpg?s=120&d=mm&r=g)
21 Jul
2009
21 Jul
'09
10:45 a.m.
On Tue, Jul 21, 2009 at 1:07 PM, Erik Huelsmann<ehuels@gmail.com> wrote:
When running this code, it takes around 1440 seconds on my PC. Then I modified the stack management routine to re-use available stack frames (and conses), instead of creating new ones on every call. This took execution time down to around 1240 seconds. A good improvement, I'd say. However, with the change described above, stack frames won't ever become garbage anymore. My question is: does the loss of GC-ability outweigh the performance gain?
How many frames will then hang around? If I make a deep call, and never do another deep call, will I then have frames lurking around from the deep call?