Gerry Seidman <[EMAIL PROTECTED]> writes: ... > I am evaluating Velocity for a mission critical application (300+ > heavy internal users + web presence for another 25,000 moderate > users and 250,000 occasioinal users). Does anyone have experience > with this type of deployment?
Yes, extensive experience. A Velocity-based web app UI scales to that level without any problem. Possible gotchas: - The default unbounded template cache can result in a high base memory footprint after all templates have been accessed. Solution: insert a bounded template cache, preferable LRU-based (I have one if you want it). - Unoptimized Java code (yours or libraries you use) called from your Velocity templates can result in poor performance. Solution: optimize your Java code and/or swap out inefficient libraries that your code relies upon. -- Daniel Rall --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
