I've always thought that Tapestry would scale nicely to very, very large applications. Now I'm a bit concerned having seen a very large application in Tapestry. Nearly 700 pages many of which have more than 5000 components. This dwarfs the other big Tapestry applications I've seen. Even with live class reloading, these people are seeing 20 - 30 seconds or more to reload a page after a change.
One thing I'm considering is changing the cache inside the PageSource service to use WeakReferences, rather than SoftReferences, for pages. I may make that optional, perhaps with a symbol "tapestry.large-application-optimizations" that could be enabled to choose which mode to run things in. Most of this will need to slip into Tapestry 5.4. What I'm seeing is that after (attempting to) load all pages, the app is quite memory starved (over 1 gb of memory usage) but the JVM doesn't seem to be evicting my soft references. I'm looking for places those references can leak. but not finding any. -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
