xanderlin
commented
10 years ago pretty sure a lot of this is from the echonotes api:
- we can probably cache the api data we're using (i think this is just beat timings)
- knowing the beat times will probably let us do mixing live (on the client end through webaudio)
- not mixing on the server will likely solve some of our cpu issues (i think on my computer it was spending 15 seconds every 25 second loop rendering)
- mixing live also removes the need for temp files entirely.
i guess this is all in the audiodaemon or the javascript player. oops. eh heh heh.
It's totally unacceptable that this application uses 500M+ of RAM and 10G+ of disk space. This makes it impossible to deploy on any box with low RAM (e.g. 512M box). We need to figure out what the heck is going on here and fix it.
Suggestions for fixes include running a cron job to delete the tmp files that keep getting created... but this doesn't solve the memory problem.