On Mon, 2008-11-10 at 10:23 +0800, Foo JH wrote: > > However, the problem of programs with GUIs in perl is that they create > > very huge programs that eat very much memory if the programs are complex > > and need to use threads. > > I've just abandoned a program in WxPerl (an RSS reader/Podcast > > reader/TV/Radio listener) because when it had one thread it occupied 40 > > MB of memory, and after adding each new thread, other 40 MB of memory > > were occupied, so at 4 threads it used 160 MB of memory, and I needed to > > add more threads for updating. > How is it that wxPerl chews up so much memory? Or is it that you kept a > lot of data in-memory? If so then that's not a failing of wxPerl. > > I wonder what is the most complex app out there (free or commercial) > written in wxPerl? >
Yes, I think threads really tend to use more and more memory. I have an application, when it runs, it takes 60 MB of memory, and a simple thread to check update increases the memory usage to 90 MB. If the user checks update once again, it increases to 120 MB. Then, we tried to use POE::Loop::Wx and we are really happy with it. When it checks for update, it increases to 71 MB, and no matter how many times a user clicks to check for update, memory usage does not increase. I hope this can help. Best Regards, bungsu
