I just turned off all the plug-ins I don't use (that's most of them). It saved me about 5 MB.
That said, I think the memory footprint is huge considering what it's doing. And I think it's something the development team should consider ... some people want to run this on small-footprint systems like slugs and linkstations. The audiotron could run itself, an MP3 decoder, a web server and keep 30,000 songs in a memory database inside a 32MB machine. My 8,000 song system here is taking over 80MB. So there's some room for improvement, balanced with the other demands other people have pointed out here - multi-platform, interpreter, etc. I expect that, in the next few releases, we're going to see the server re-architected so that the highly machine-interactive parts (tending to the hardware, streaming music) can run on one processor, close to the hard disk (or if it's all on one processor, this process runs at high priority), the user interface could run at a medium priority, perhaps in a different processor, and the background stuff (scanning tags on new songs that show up, etc) at a low priority. That would help the readability of that code, because all the dispatch-yourself code could be stripped out, replaced by real OS style dispatching (or a Slim dispatcher). -- Michaelwagner _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
