From: "Foo JH" <[EMAIL PROTECTED]> >> 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 don't keep too much data in the memory. I have the main thread that draws the GUI, another thread that downloads the RSS feeds and update an SQLite database, another thread that updates the screen with the new RSS feeds from the database, and another thread that runs a web server. But even a very simple program that uses WxPerl occupies around 10 MB of RAM if I remember well, and this is very much. But my main problem is not the memory but the fact that that program that uses threads is very slow responsive, even though I run it on a Intel Core 2 Duo at 3 GHZ. > I wonder what is the most complex app out there (free or commercial) > written in wxPerl? I would also like to know this... Octavian
