with SessionSizeDebugPanel, it displays session
size and totalSize (by SessionTotalSizeModel). Does this totalSize includes
size of object loaded by LDM or it counts all components and models size in
detached state?
--
Daniel
() then it will be kept alive in the http session.
When we are using DebugBar with SessionSizeDebugPanel, it displays session
size and totalSize (by SessionTotalSizeModel). Does this totalSize includes
size of object loaded by LDM or it counts all components and models size in
detached state?
I have to check
with SessionSizeDebugPanel, it displays
session
size and totalSize (by SessionTotalSizeModel). Does this totalSize
includes
size of object loaded by LDM or it counts all components and models size
in
detached state?
I have to check what is th difference between size and totalSize, but since
https
is not required.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/DataView-and-increasing-session-size-tp1876757p4652739.html
Sent from the Users forum mailing list archive at Nabble.com
Get a heapdump, use yourkit/visualvm.
On Mon, Jul 16, 2012 at 11:14 AM, Ian Marshall ianmarshall...@gmail.com wrote:
I don't think that I am getting the session size in the right place. Despite
my session sizes being logged as very small at ~1.7kB using the Google App
Engine (GAE) web
Thanks for the tip, Jochen.
I'm already doing that now, using Oracle's Java VisualVM
Jochen Mader wrote
Get a heapdump, use yourkit/visualvm.
On Mon, Jul 16, 2012 at 11:14 AM, Ian Marshall lt;IanMarshall.UK@gt;
wrote:
I don't think that I am getting the session size in the right
I don't think that I am getting the session size in the right place. Despite
my session sizes being logged as very small at ~1.7kB using the Google App
Engine (GAE) web development server, in GAE production I am getting session
sizes approaching 1MB (and attempting to breach this GAE-imposed limit
Hello,
Is there a good way to discover my serialised or about-to-be-serialised
session size without adding the debug bar to my page?
I currently use
@Override
protected void onAfterRender()
{
super.onAfterRender();
CloudSession ssnSession = (CloudSession)getSession();
long
Override Session#onDetach() and do it before calling super.onDetach().
On Fri, Jul 13, 2012 at 2:01 PM, Ian Marshall ianmarshall...@gmail.com wrote:
Hello,
Is there a good way to discover my serialised or about-to-be-serialised
session size without adding the debug bar to my page?
I
Thanks Martin,
I could not find onDetach() but found detach() so I have done this in my
WebSession subclass:
@Override
public void detach()
{
long loSize = getSizeInBytes();
m_logger.log(Level.FINE, String.format(Session size = %,dB., loSize));
super.detach();
}
This seems
Thanks Jeremy, works great!!!
On 23/06/12 23:23, Jeremy Thomerson wrote:
On Fri, Jun 22, 2012 at 11:28 PM, Walter Rugora m...@sudus.eu wrote:
Hi,
when I apply the Wicket 1.3 way to determine session size,
RequestCycle.get().getSession().getSizeInBytes()
it results in an around 3000bytes
On Fri, Jun 22, 2012 at 11:28 PM, Walter Rugora m...@sudus.eu wrote:
Hi,
when I apply the Wicket 1.3 way to determine session size,
RequestCycle.get().getSession().getSizeInBytes()
it results in an around 3000bytes value in my case. And adding or
removing Labels changed the session size
Hi,
when I apply the Wicket 1.3 way to determine session size,
RequestCycle.get().getSession().getSizeInBytes()
it results in an around 3000bytes value in my case. And adding or
removing Labels changed the session size.
Now with Wicket 1.5 using
Session.get().getSizeInBytes()
session size
Hi there,
for Wicket 1.3 I determine session size like this:
RequestCycle.get().getSession().getSizeInBytes()
But the RequestCycle underwent some changes and I cannot figure out how
to do it for Wicket 1.5?
Appreciate your help!
Walter
session size like this:
RequestCycle.get().getSession().getSizeInBytes()
But the RequestCycle underwent some changes and I cannot figure out how
to do it for Wicket 1.5?
Appreciate your help!
Walter
-
To unsubscribe, e-mail
Session.get().getSizeInBytes();
-Tom
On 19.06.2012 at 13:03 Walter Rugora wrote:
Hi there,
for Wicket 1.3 I determine session size like this:
RequestCycle.get().getSession().getSizeInBytes()
But the RequestCycle underwent some changes and I cannot figure out how
to do it for Wicket
On Tue, Jun 19, 2012 at 2:10 PM, Thomas Götz t...@decoded.de wrote:
Session.get().getSizeInBytes();
Apparently it is not removed ...
-Tom
On 19.06.2012 at 13:03 Walter Rugora wrote:
Hi there,
for Wicket 1.3 I determine session size like this:
RequestCycle.get().getSession
determine session size like this:
RequestCycle.get().getSession().getSizeInBytes()
But the RequestCycle underwent some changes and I cannot figure out how
to do it for Wicket 1.5?
Appreciate your help!
Walter
-
To unsubscribe
I've been working in wicket for awhile now. I was just reading this post last
night.
http://www.small-improvements.com/10-things-about-apache-wicket-i-love/wicket:pageMapName/wicket-0
I was intrigued by the comment that more extensive use of Model would reduce
session size.
Why would
On Tue, 19 Jun 2012 14:01:13 -0500
Douglas Ferguson the...@gmail.com wrote:
I was intrigued by the comment that more extensive use of Model
would reduce session size.
Why would this be? Won't models still wind up in the data graph for
the Page and thus be in the pagemap?
Well, apart from
Yes.. LoadableDetachable makes more sense.
Douglas
On Jun 19, 2012, at 2:17 PM, Carl-Eric Menzel wrote:
On Tue, 19 Jun 2012 14:01:13 -0500
Douglas Ferguson the...@gmail.com wrote:
I was intrigued by the comment that more extensive use of Model
would reduce session size.
Why would
be integrated into the core.
Josh.
On Mon, Feb 20, 2012 at 5:32 AM, robmcguinness
robert.mcguinness@gmail.com wrote:
very nice thanks!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Shrinking-the-session-size-simp
ly-by-zipping-it-Saved-my-day
this message in context:
http://apache-wicket.1842946.n4.nabble.com/Shrinking-the-session-size-simp
ly-by-zipping-it-Saved-my-day-tp4402980p4403065.html Sent from the
Users
forum mailing list archive at Nabble.com
Hi all,
thought I'd share a really simple hack that we're using to reduce the Wicket
session size (on Wicket 1.4).
Background: We deploy to Google App Engine, and there's a strict 1MB limit.
We've been using LDMs and all sorts of optimisations, but we were still
reaching the limits when a user
very nice thanks!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Shrinking-the-session-size-simply-by-zipping-it-Saved-my-day-tp4402980p4403065.html
Sent from the Users forum mailing list archive at Nabble.com
Thanks for the post.
I wish this could be integrated into the core.
Josh.
On Mon, Feb 20, 2012 at 5:32 AM, robmcguinness
robert.mcguinness@gmail.com wrote:
very nice thanks!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Shrinking-the-session-size-simply
...@hamburg.de
Hi Antoine,
I have started collecting my hints over here:
http://www.small-improvements.com/blog/technical/tuning-wicket-session-size
Please note that much of it may be considered hacks and bad practice (I
am just a Wicket user, not a Wicket master). There may be better ways
with a couple of hints once I stop drowning in work.
Cheers,
Per
Reading in the other thread that a session size of 100K or less
is achievable, I'll admit defeat now: I have not been able to shrink
some of
my pages(!) to less than 200K, not to mention the sessions. Despite
LDMs
Hi Antoine,
I have started collecting my hints over here:
http://www.small-improvements.com/blog/technical/tuning-wicket-session-size
Please note that much of it may be considered hacks and bad practice (I
am just a Wicket user, not a Wicket master). There may be better ways to
achieve
Per,
Awesome summary. Much obliged.
Rob
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Just-100K-per-session-That-would-be-my-dream-come-true-Anyone-here-who-has-tuned-session-size-before-tp3308014p3330455.html
Sent from the Users forum mailing list archive
this message in context:
http://apache-wicket.1842946.n4.nabble.com/Just-100K-per-session-That-would-be-my-dream-come-true-Anyone-here-who-has-tuned-session-size-before-tp3308014p3330455.html
Sent from the Users forum mailing list archive at Nabble.com
:
http://www.small-improvements.com/blog/technical/tuning-wicket-session-size
Please note that much of it may be considered hacks and bad practice (I
am just a Wicket user, not a Wicket master). There may be better ways to
achieve the same results. I'd love to get feedback on these suggestions
session size before?)
Hi Antoine,
I have started collecting my hints over here:
http://www.small-improvements.com/blog/technical/tuning-wicket-session-size
Please note that much of it may be considered hacks and bad practice (I
am just a Wicket user, not a Wicket master). There may be better
'
version so I can check back?
From: Per p...@hamburg.de
To: users@wicket.apache.org
Date: 03/01/2011 02:22 PM
Subject:Re: Just 100K per session? That would be my dream come
true! (Anyone here who has tuned session size before?)
Hi Antoine,
I have started collecting my
We have a modal window (not matter Panel oder Page as content) which
holds a lot of AjaxLinks. Each time an AjaxLink is clicked the session
grows. Is there a way to suppress the versioning of the session and
page? It's the PageMap that is growing.
The ModalWindow does not hold any explicit
I have experienced memory problems before with Page backed ModalWindow, so
I'd recommend Panel backed.
About versioning see Component.setVersioned(false).
On Fri, Feb 25, 2011 at 11:45 AM, Stefan Lindner lind...@visionet.dewrote:
We have a modal window (not matter Panel oder Page as content)
]
Gesendet: Freitag, 25. Februar 2011 10:55
An: users@wicket.apache.org
Betreff: Re: Session size with ModalWindow
I have experienced memory problems before with Page backed ModalWindow, so I'd
recommend Panel backed.
About versioning see Component.setVersioned(false).
On Fri, Feb 25, 2011 at 11
Grigorov [mailto:mgrigo...@apache.org]
Gesendet: Freitag, 25. Februar 2011 10:55
An: users@wicket.apache.org
Betreff: Re: Session size with ModalWindow
I have experienced memory problems before with Page backed ModalWindow, so
I'd recommend Panel backed.
About versioning see
Sigh! Ok, thank you for the below example. I will dig into the memory pool.
Stefan
-Ursprüngliche Nachricht-
Von: Martin Grigorov [mailto:mgrigo...@apache.org]
Gesendet: Freitag, 25. Februar 2011 11:20
An: users@wicket.apache.org
Betreff: Re: Session size with ModalWindow
I guess you
. Admittedly, this
comes at the expense of flexibility and beauty, but I'm only doing this
in the inner loops of very few pages, so who cares :-) Will write a
summary with a couple of hints once I stop drowning in work.
Cheers,
Per
Reading in the other thread that a session size of 100K or less
Reading in the other thread that a session size of 100K or less
is achievable, I'll admit defeat now: I have not been able to shrink some of
my pages(!) to less than 200K, not to mention the sessions. Despite LDMs,
CompoundPropertyModels, and no, there are no domain objects
How are you storing/retrieving your photos? I recently did some session
size testing and I found the sessions were surprisingly small. Once I
removed the detachable model wrapped around an object holding a photo
(byte array) retrieved from the database my session size shot up
considerably
issues, despite weeks of research and
profiling. Reading in the other thread that a session size of 100K or less
is achievable, I'll admit defeat now: I have not been able to shrink some of
my pages(!) to less than 200K, not to mention the sessions. Despite LDMs,
CompoundPropertyModels
may have many Gigs these
days, you'd still be in trouble if thousands of users came slurping 40M
each, that's why I do think that session size remains an important
consideration. I would strongly recommend anyone not to leave
optimisation till the very last, but plan ahead and spike some
So I still haven't solved my memory issues, despite weeks of research and
profiling. Reading in the other thread that a session size of 100K or less
is achievable, I'll admit defeat now: I have not been able to shrink some of
my pages(!) to less than 200K, not to mention the sessions. Despite
and
profiling. Reading in the other thread that a session size of 100K or less
is achievable, I'll admit defeat now: I have not been able to shrink some of
my pages(!) to less than 200K, not to mention the sessions. Despite LDMs,
CompoundPropertyModels, and no, there are no domain objects
!
-Original Message-
From: Jeremy Thomerson [mailto:jer...@wickettraining.com]
Sent: Monday, January 17, 2011 5:33 PM
To: users@wicket.apache.org
Subject: Re: session size
Okay, so you are storing *every* page in your page map in session. So,
here's your next path (already partially
On Thu, Jan 20, 2011 at 2:42 AM, Mihai Toma mihai.t...@asf.ro wrote:
Hi guys!
I resolved the problem.
Here is what I was doing:
- I have a page, let's say HomePage which extends WebPage.
- This HomePage add a MenuPanel which extends Panel (add(new MenuPanel()).
- This MenuPanel add a
Hi!
I have an application build with wicket and I have a session problem.
If one user browse the application the session (the object WebSession)
becomes bigger and bigger, so if I browse 20 pages the session size has
around 16 Mb.
When I start browsing the session has something less than
:
Hi!
I have an application build with wicket and I have a session problem.
If one user browse the application the session (the object WebSession)
becomes bigger and bigger, so if I browse 20 pages the session size has
around 16 Mb.
When I start browsing the session has something less
an application build with wicket and I have a session problem.
If one user browse the application the session (the object WebSession)
becomes bigger and bigger, so if I browse 20 pages the session size has
around 16 Mb.
When I start browsing the session has something less than 100 Kb.
I read
problem.
If one user browse the application the session (the object WebSession)
becomes bigger and bigger, so if I browse 20 pages the session size has
around 16 Mb.
When I start browsing the session has something less than 100 Kb.
I read some things about the pages which
Yes, I use HttpSessionStore.
-Original Message-
From: Jeremy Thomerson [mailto:jer...@wickettraining.com]
Sent: Monday, January 17, 2011 5:20 PM
To: users@wicket.apache.org
Subject: Re: session size
Are you using HttpSessionStore (this is not the default - which means you
would have
...@wickettraining.com]
Sent: Monday, January 17, 2011 5:20 PM
To: users@wicket.apache.org
Subject: Re: session size
Are you using HttpSessionStore (this is not the default - which means you
would have to explicitly set this up in your application class)?
On Mon, Jan 17, 2011 at 8:41 AM, Martin Grigorov
Thanks for your recommendations.
-Original Message-
From: Jeremy Thomerson [mailto:jer...@wickettraining.com]
Sent: Monday, January 17, 2011 5:33 PM
To: users@wicket.apache.org
Subject: Re: session size
Okay, so you are storing *every* page in your page map in session. So,
here's your
Hi all,
I was debugging my sessions size in order to reduce it and I saw that one of
my page spend 20ko because of an dynamic image generated with JFreeChart.
JFreeChart was serialized with my DynamicImageRessource.
My first optimisation is to make JFreeChart a static field initialized in a
Then this image will to be the same for all sessions. If you don't want that
object on your session, make sure at getImageData method implementation that
you are always creating your chart object, and not keeping it in any
instance variable.
On Thu, Jan 28, 2010 at 8:28 AM, Gaetan Zoritchak
In fact, I just put the reference to JFreeChart as static. All the commons
values are initialized in the static bloc (ie, Font, definition on the axis,
...).
I keep the image generation done in the getImageData using the
pageParameters. So every session or even page request can have its own
Gaetan,
You can mark whatever instance that is causing the session to be so large as
'transient' to avoid it being serialized -- you'd have to recreate it each
time it was needed though. So if it's in your model:
=
private String chartName;
private String chartArguments; // maybe
Hi all,
I'm monitoring my Wicket app via the RequestLogger and going through
making improvements where needed. I am wondering what the size of a
session would be before it is considered too large? Is the value given
in the 'sessionsize' attribute of the logging output a reasonable way
to
Sessionsize recording is rather expensive, I wouldn't turn that on
unless you're hunting for something. So the request times should be
taken with a jar of salt.
Session size per se is not the only factor. A session size of 1MiB can
be perfectly ok, which would still support 1k users on one box
there are two things to take into account: memory and network
like martijn said, a session is too big when it is greater then
available heap/target number of users
if you are using session replication for clustering or failover the
session is too big when the time to replicate it becomes a
of entities and so I am
using
a DataView together with LoadableDetachableModels to read the data on
demand.
However, when looking at the serialized sessions, I can observe that
the
session size constantly increases by a fairly large amount although I
am
just using the navigator to page through
is supposed to
work.
In my
application, I have to show quite large list of entities and so I
am
using
a DataView together with LoadableDetachableModels to read the data
on
demand.
However, when looking at the serialized sessions, I can observe
that
the
session size constantly
the DataView component is supposed to
work.
In my
application, I have to show quite large list of entities and so I
am
using
a DataView together with LoadableDetachableModels to read the data
on
demand.
However, when looking at the serialized sessions, I can observe
that
the
session size constantly
.
In my
application, I have to show quite large list of entities and so I
am
using
a DataView together with LoadableDetachableModels to read the
data
on
demand.
However, when looking at the serialized sessions, I can observe
that
the
session size constantly increases by a fairly
sessions, I can observe
that
the
session size constantly increases by a fairly large amount
although
I
am
just using the navigator to page through the list. Also, when
looking
into
the serialized session, I can see that the objects that are
supposed
to
be reloaded on demand are serialized
that the
session size constantly increases by a fairly large amount although I am
just using the navigator to page through the list. Also, when looking into
the serialized session, I can see that the objects that are supposed to
be reloaded on demand are serialized into the session as well
of entities and so I am using
a DataView together with LoadableDetachableModels to read the data on
demand.
However, when looking at the serialized sessions, I can observe that the
session size constantly increases by a fairly large amount although I am
just using the navigator to page through
the DataView component is supposed to work. In my
application, I have to show quite large list of entities and so I am using
a DataView together with LoadableDetachableModels to read the data on
demand.
However, when looking at the serialized sessions, I can observe that the
session size constantly
the DataView component is supposed to work.
In my
application, I have to show quite large list of entities and so I am
using
a DataView together with LoadableDetachableModels to read the data on
demand.
However, when looking at the serialized sessions, I can observe that
the
session size
with LoadableDetachableModels to read the data on
demand.
However, when looking at the serialized sessions, I can observe that
the
session size constantly increases by a fairly large amount although I
am
just using the navigator to page through the list. Also, when looking
into
the serialized session
is supposed to work.
In my
application, I have to show quite large list of entities and so I am
using
a DataView together with LoadableDetachableModels to read the data on
demand.
However, when looking at the serialized sessions, I can observe that
the
session size constantly increases
quite large list of entities and so I am
using
a DataView together with LoadableDetachableModels to read the data on
demand.
However, when looking at the serialized sessions, I can observe that
the
session size constantly increases by a fairly large amount although I
am
just using
Hi!
This is not a direct wicket question, but important for wicket usage, so
I'm asking here...
What you use to monitor Tomcat sessions size? (preferable something that
I can use in production)
I tried with JMX/jconsole and with LambdaProbe. The former doesn't seems
to have that info, and
you can monitor what wicket does with the IRequestLogger
On Mon, Dec 1, 2008 at 16:13, Adriano dos Santos Fernandes
[EMAIL PROTECTED] wrote:
Hi!
This is not a direct wicket question, but important for wicket usage, so
I'm asking here...
What you use to monitor Tomcat sessions size?
So does that mean there is nothing already made to monitor session size
at container level instead of application level?
Adriano
Johan Compagner escreveu:
you can monitor what wicket does with the IRequestLogger
On Mon, Dec 1, 2008 at 16:13, Adriano dos Santos Fernandes
[EMAIL PROTECTED
On Thu, 10 Jul 2008, Johan Compagner wrote:
try it with yourkit?
I've got JProfiler and at least with that it's been a bit
difficult to pinpoint which exactly are the components
hanging onto the biggest objects.
But I did a kludge in our own DiskPageStore extension where
I visit all the
This also revealed that for example the page instance I'm
currently looking at has more than 2000 components in total
:) Maybe we should look at replacing some stuff that is not
displayed with dummy WebMarkupContainers instead of relying
on visibility control.
Maurice and Martijn have a
try it with yourkit?
i know it is still a bit of work but normally if you do a request and after
the request you look at the HttpSession
and see how big it is, you should be able to pin point the biggest retained
size
johan
On Thu, Jul 10, 2008 at 5:24 AM, Timo Rantalaiho [EMAIL PROTECTED]
Hello,
I'm currently debugging a situation where we have too much
data in the session (in some places, more objects should be
behind detachable models, smaller object graphs retrieved
from the db etc). I've added debug logging to get the size
of the page just before storing it in DiskPageStore
reference other Pages and the
session size changes as it should. However, occasionally when we open
pages in a new tab (often when multiple pages are opened in a new tab in
rapid succession), we get the following situation:
1 tab
pagemap-null size = x
2 tabs
pagemap-null size = 2x
pagemap-0 size
though
unfortunately we can't consistently reproduce it. We're using Wicket
1.3.1 with automatic multi-window support enabled and the default
SecondLevelCacheSessionStore.
During normal use of our site, no Pages reference other Pages and the
session size changes as it should
.
During normal use of our site, no Pages reference other Pages and the
session size changes as it should. However, occasionally when we open
pages in a new tab (often when multiple pages are opened in a new tab in
rapid succession), we get the following situation:
1 tab
pagemap-null
times
though
unfortunately we can't consistently reproduce it. We're using
Wicket
1.3.1 with automatic multi-window support enabled and the default
SecondLevelCacheSessionStore.
During normal use of our site, no Pages reference other Pages and
the
session size changes
there,
we're developing a rather straight forward application with wicket and I
am
wondering if it is ok to call setResponsePage(getPage()) inside the
onClick() method of a Link? Because the session size is constantly
increasing, here's my example:
Application class:
public class TestApplication
the
onClick() method of a Link? Because the session size is constantly
increasing, here's my example:
Application class:
public class TestApplication extends WebApplication {
public TestApplication() {
super();
}
@Override
public Class
:
Hi there,
we're developing a rather straight forward application with wicket and
I
am
wondering if it is ok to call setResponsePage(getPage()) inside the
onClick() method of a Link? Because the session size is constantly
increasing, here's my example:
Application class
the
onClick() method of a Link? Because the session size is constantly
increasing, here's my example:
Application class:
public class TestApplication extends WebApplication {
public TestApplication() {
super();
}
@Override
:
Hi there,
we're developing a rather straight forward application with wicket
and
I
am
wondering if it is ok to call setResponsePage(getPage()) inside the
onClick() method of a Link? Because the session size is constantly
increasing, here's my example
I'm using trunk right now and the issue is resolved, the session size does
not increase anymore when setting the response page. Since this was a
critical one on our issue tracking, thanks for the quick fix.
I opened jira https://issues.apache.org/jira/browse/WICKET-1036 WICKET-1036
and I'll
Hi there,
we're developing a rather straight forward application with wicket and I am
wondering if it is ok to call setResponsePage(getPage()) inside the
onClick() method of a Link? Because the session size is constantly
increasing, here's my example:
Application class:
public class
92 matches
Mail list logo
