Let me try and give you a better picture of what is happening. We have a Page (which is a Velocity Template) not much on it but a bunch of sets. The page parses the template (also a Velocity Template) this has HTML and parses 0 to many containers. The container (also a Velocity Template) loops over and parses Content. Each content is a Velocity Template.
In my example I have a page with one container and 500 pieces of content in it. If I hit in the browser it all works but is a bit slow first time. Then it is in cache and is not too bad. It should also be mentioned that the parses are actually Merges template.merge() If I put load using siege or jmeter it totally breaks down as I described. The debugger isn't tellme me a whole lot. I will attach a thread dump and some of the velocity files. I know I am in cache and h2 but notice all the http://pastebin.com/pg42QGue Now the velocity being hit This is the page http://pastebin.com/AMm8wxyf The template http://pastebin.com/BG8CA0HF The container http://pastebin.com/3g4UL6KT and then 500 contents that look like this http://pastebin.com/feN26eEK what happens is each content gets merged. Thanks, Jason Tesser dotCMS Lead Development Manager 1-305-858-1422 On Mon, Sep 13, 2010 at 12:11 PM, Nathan Bubna <nbu...@gmail.com> wrote: > On Mon, Sep 13, 2010 at 8:47 AM, Jason Tesser <jasontes...@gmail.com> wrote: >> Question for you >> >> My velocityengine is a singletons right now. >> >> Could having multiple VelocityEngines help? Could I be up against some >> limit here under load? > > Without knowing more about what is going on, it's really hard to say. > It would help to know more. I still struggle to imagine what is > causing things to hang at that line. You say you were using 1.6.3? > Because line 3391 in Parser.java doesn't look like that in 1.6.3, > 1.6.4 or the trunk. I'd like to see the surrounding code, to see if i > can understand better what is happening. Does your debugger tell you > anything else? Like how many Parser objects exist at the time? Are > there any other choke points? Are you seeing "Created <X> parsers." > debug output in your logs? > > And you could always just try using multiple engines and see if it > helps. Depending on how difficult that refactor is, sometimes guess > and check really is the fastest way to a solution. :) > >> Thanks, >> Jason Tesser >> dotCMS Lead Development Manager >> 1-305-858-1422 >> >> >> >> On Mon, Sep 13, 2010 at 11:40 AM, Nathan Bubna <nbu...@gmail.com> wrote: >>> it kinda sounds like the stuck threads are waiting for a lock to be >>> released. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org >> For additional commands, e-mail: user-h...@velocity.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org > For additional commands, e-mail: user-h...@velocity.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org For additional commands, e-mail: user-h...@velocity.apache.org
