What about this:
Index: wicket/src/java/wicket/markup/html/link/PageLink.java
===
--- wicket/src/java/wicket/markup/html/link/PageLink.java (revision 6861)
+++ wicket/src/java/wicket/markup/html/link/PageLink.java (working
We could change that a bit.But only if the pagelink was not created with an page instance alreadyBecause if you use the contructor:new PageLink("xx", myPageInstance)then we really need to serve that page instance..
Maybe if we added a method to IPageLink so that we can ask what it really has (the c
I mean when the PageLink is instantiated using PageLink(String, Class)
of course.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
-
Using Tomcat but need to do more? Need to support web services,
* Eelco Hillenius:
> It's an optimization.
So you confirm that PageLink is not optimized for stateless
webapps.
Reading the PageLink code, I wonder why setResponsePage(Page) is used instead
of setResponsePage(Class):
public void onClick()
{
// Set page source's p
It's an optimization. So it depends on the kind of application you're
building whether you 'need' it. Typically, I'd consider using
bookmarkable pages for pages that have to be accessible regardless of
any session (e.g. a bookmark). You can code your whole app using
bookmarkable pages, but you will
* Johan Compagner:
> setResponsePage(Page) can be used just fine. Except you have to
> do then setRedirect(false) because if you redirect it (what is
> default when for example submitting a form) then the page is
> statefull because it has to be there after the redirect so that
> we can re
setResponsePage(Page) can be used just fine.Except you have to do then setRedirect(false)because if you redirect it (what is default when for example submitting a form)then the page is statefull because it has to be there after the redirect so that we can render it.
johanOn 8/10/06, Jean-Baptiste Q
* Eelco Hillenius:
> > How can I set a page to be stateless in 1.2.1 ? Is there some attribute to
> > do this or does it just mean that you use detachable models?
>
> Stateless means the page isn't even stored in the session. We started
> out implementing that automatically for pages that don't h
> The problem is also that the CPU was on 100%.Hmm, that's interesting. We (or rather Johan and Jonathan) really
worked hard at making Wicket as efficient as possible. Even with thewhole object tree creation etc it should still perform very well. Ifyou find certain hotspots, please share.I think th
> It died after eating 100MB of memory and serving 600-800 requests*100
> threads.
That is probably because - like said elsewhere in this thread - a new
session was started for every request.
> The problem is also that the CPU was on 100%.
Hmm, that's interesting. We (or rather Johan and Jonatha
the advantage that wicket provides in session handling is that it evicts objects from it for you. what you had to put into a session in lets say a struts app to be accessed across requests you now put into a Page and pass references from page instance to page instance if it is needed across pages.
> It sure seems that sessions are used heavily, but i knew that anyway,
> from documentation.
>
I don't think that sessions are used heavily compared to other
web-apps. The difference is that Wicket does most of the Sessions
tasks for you and it is consistent whereas with Struts etc you end up
doi
The cookies are not handled. Every request creates a new session.
I didn't say that this is a representative case for anything, just a
simple test that should not be taken very seriously and as I
mentioned, the webapp didn't crash when I used datachable models.
On 8/9/06, Gwyn Evans <[EMAIL PROTEC
> Well.. ab2 is an apache benchmarking tool. But I'm under the impression
> that it's intended to measure the performance of static pages.
Yep, it's mostly used for creating traffic. Just a basic test of
performance. The description of AB is:
ab is a tool for benchmarking your Apache Hypertext Tra
http://httpd.apache.org/docs/2.2/programs/ab.html
I think you're correct with the params, but I've no idea about the cookies.
I think that basic lesson is that the benchmark that was done is only
of use if the OP intended to be serving the Wicket-Examples app out at
that rate - otherwise a more r
Well.. ab2 is an apache benchmarking tool. But I'm under the impression
that it's intended to measure the performance of static pages.
It doesn't use cookies, does it? If I recall correctly there should be a
possibility to specify a cookie value there, so you might be able to
reduce the number
What is ab2 for a thing?It looks like you are 1000 times getting that same bookmarkable page for 100 threads?That page is because of the source code viewer link not stateless so you a creating pages that will go into the sessions.
Now is the question does ab2 work with cookies or not? If not then i
As Johan said, no. Take a look at the Javadocs for
BookmarkablePageLink & WebPage (links below)
/Gwyn
http://wicket.sourceforge.net/apidocs/wicket/markup/html/link/BookmarkablePageLink.html
http://wicket.sourceforge.net/apidocs/wicket/markup/html/link/BookmarkablePageLink.html
On 09/08/06, Korb
t 2006 11:39An:
wicket-user@lists.sourceforge.netBetreff: Re: [Wicket-user]
Performance/Scalability tips
I also stress tested the examples quite a lot. Which part
did you test that you get an out of memory? And how much memory did you give
your server?Memory usage can be cut down in sev
On 09/08/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
> where did you read about the detached models ?
Here's a good place to start -
http://www.wicket-wiki.org.uk/wiki/index.php/Models#Detachable_Models.
Then check the entries for the specific classes (e.g.
AbstractDetachableModel) mentioned e
He Sebastjan,
where did you read about the detached models ?
Regards
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von
Sebastjan TrepcaGesendet: Mittwoch, 9. August 2006
10:17An: wicket-user@lists.sourceforge.netBetreff:
[Wicket-user] Performance
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Johan
CompagnerGesendet: Mittwoch, 9. August 2006 11:39An:
wicket-user@lists.sourceforge.netBetreff: Re: [Wicket-user]
Performance/Scalability tips
I also stress tested the examples quite a lot. Which part
did you test that
I used the default resin3pro configuration. I tested it like this:ab2 -n 1000 -c 100 http://localhost:8080/wicket-examples-1.2/repeater?wicket:bookmarkablePage=:wicket.examples.repeater.DataGridPage
It died after eating 100MB of memory and serving 600-800 requests*100 threads. The problem is also t
I also stress tested the examples quite a lot. Which part did you test that you get an out of memory? And how much memory did you give your server?Memory usage can be cut down in several ways:1> use for heavy hit pages stateless pages (in
1.2 just use bookmarkable links and no forms on it), in 2.0
There's this on the subject that Martijn posted a little while ago,
http://www.nabble.com/Re%3A-Wicket-in-large-scale-production-scenarios--p5374359.html
but maybe someone on the list might have more comments.
The main technical issues are to ensure that you use detatched models
& to try & be care
Hi all!We're starting a new project that will be quite big (1-2 million users) so now I'm choosing a web framework to use. It seems that Wicket is a very good framework but what worries me is the performance and scalability. I installed wicket-examples on my machine and stress-tested them a bit, ju
26 matches
Mail list logo
