Sorry to say, the last_compile_time check is ineffective in this situation.
For reference, I'm running Ubuntu desktop on a Q6600 with 4 gig ram. Erlang is version 5.6.4, [64-bit], [smp:4], [hipe]. I just started working on a simple app and there is no real code in any of the controllers or views. Here's all the things that seem to contribute to this issue. 1. The current code checks if last compile time was more than 3 (hardcoded) seconds ago. 2. There are 10 components - all views and controllers using erlyweb_magic which affects size of <appname>_erlyweb_data 3. smerl:compile on <appname>_erlyweb_data takes close to 6 seconds The long compile means it slips through the last_compile_time check and will recompile multiple times when there are redirects - meaning 12+ second waits. I removed all the erlyweb_magic and this drops the erlyweb_data compile time down significantly but that defeats the purpose. I'm trying to get a simple app up and running and want to use as much leverage as possible. The erlyweb_data is dependent on whether something in the controllers/ views changed so here's some potential solutions. 1. Track whether a controller/view was recompiled and force recompile on erlyweb_data if needed 2. Delete the erlyweb_data beam file when a controller/view is recompiled and then later trigger erlyweb_data recompile if the beam isn't there 3. Check timestamps on the controller/view beam files and recompile erlyweb_data if it doesn't have the most current timestamp Other ideas? Did I miss something? thanks, michael. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
