Are there any articles comparing JSF performance with JSP for relatively
up-to-date JSF implementations? Specifically I'm interested in data table
rendering...
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073426#4073426
Reply to the post :
Tapestry has some advantages over JSF. One of them is performance.
AFAIK it compiles code against bean code so no reflection overhead +
more errors can be discovered at compile time compared to facelets.
JSF performance is one of the issues which prevents its wider adoption.
JSF also requires much
Based in my experience with production applications, JSF is not a significant
performance concern. I don't know if that is true across the board, but that's
my experience. Honestly, I would suspect the overhead of Seam itself is larger
than the overhead of JSF, but again I don't see any
Reflection by itself should not introduce a big performance hit. As Norman
said, Seam uses much more reflection than JSF. Yet, in our tests, adding Seam
only decrease performance by 5% to 10%.
The big performance problem in JSF is the need to serialize objects. You can
reduce that by using
We always use server side state saving but still observe slow performance with
JSF. I'm pretty sure it is attributed to JSF (and not Seam). JSF needs to
operate on a tree of components (do various searches on it) and there are 6
phases when it could do that. There seems to be some HTML
So, mgrouch, are you volunteering to help us out with Tapestry integration? :)
It should not be too hard since as Norman indicated, the Seam core has no
dependency on JSF ...
Do you want to give it a try? We'd appreciate it. :)
View the original post :
My current work schedule makes it impossible. Might be someone from tapestry
developers team would be interested in doing it...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072754#4072754
Reply to the post :
BTW in tapestry 5 they are building brand new IoC controller based on
annotations and javassist byte code manipulation. Might be you guys
could convince them to stop doing it and just use Seam for it.
View the original post :
mgrouch wrote : All of it makes it (in my experience) 5 times slower than
same tasks with JSP.
|
Do you mean your 200ms task involving html, ejb, database access now takes 1s,
or do you mean your 200ms now takes 220ms?
View the original post :
Unfortunately 200ms * 5 times = 1 sec
:(
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072762#4072762
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072762
___
jboss-user mailing
AFAIR
Apply request values JSF phase on big JSF form for whatever reason was the
longest. Even longer than DB access.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072764#4072764
Reply to the post :
That is not typical. There's not enough to tell exactly what is wrong, but
it's definitely not indicative of normal JSF performance.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072800#4072800
Reply to the post :
These are different paradigms.
I have used tapestry and Seam (JSF) and Seam has a number of significant
advantages over tapestry in my opinion...
I would recommend you do a spike of your main program thread in both Seam and
Tapestry and by then you would be able to tell for yourself.
A point
Sorry...
reference implementation
Thats a bit strong.. but it's helping form the spec I believe.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072283#4072283
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072283
As far as I know, nobody has looked at Tapestry support. Seam core is more and
more separate from JSF now (see the GWT support) that it wouldn't surprise me
if it is close to being a reasonable thing. My personal recommendation is to
stick with JSF. I have nothing bad to say about Tapestry,
Yes you can. But you'll need to do some extra work integrating Tapestry with
Seam.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072288#4072288
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072288
Seam doesn't support injection into servlets ans JSP lifecycle methods.
It only does it for JSF. Would it possible (or make sense) to have this type of
functionality?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072293#4072293
Reply to the post :
You can use the seam filter to make sure you have seam initialized around a
servlet. I suppose it wouldn't take much effort to add another filter to
handle bijection, but I'm not entirely sure why someone would want to do that.
View the original post :
18 matches
Mail list logo
