Actually Robert, I'd love it if you could patch/override T5 core just
enough to disable SoftReferences and re-run your test. The results may
surprise you. I could almost guarantee you'd see the same performance
pattern for any modern jpa 2.x application. At 1.2GB, it doesn't look like
your test set
A configurable cache might be ok but what Robert is showing is a highly
typical performance degradation pattern for any sufficiently large Java
application. Tapestry's page cache is hardly the only place where soft
references are used. When your memory budget is too small, most system
engineers wou
Github https://github.com/tynamo/tapestry-security, might just as well.
Kalle
On Wed, Apr 1, 2015 at 1:29 PM, George Christman
wrote:
> Should I file a bug with tynamo jira?
> On Apr 1, 2015 3:40 PM, "Kalle Korhonen"
> wrote:
>
> > On Wed, Apr 1, 2015 at 9:22 AM, George Christman <
> gchrist..
I'm feeling that Robert is making a very good case here. I could imagine a
page-level annotation to either enable or disable evication of a page
instance after a period of time ... but that can come later. I do think
that hard-caching of pages will leading to more predictable response
performance.
Should I file a bug with tynamo jira?
On Apr 1, 2015 3:40 PM, "Kalle Korhonen" wrote:
> On Wed, Apr 1, 2015 at 9:22 AM, George Christman
> wrote:
>
> > Kalle, when I switch from
> >
> >
> configuration.add(factory.createChain("/timesheet/**").add(factory.authc()).build());
> > to
> > @RequiresUs
On Wed, Apr 1, 2015 at 9:22 AM, George Christman
wrote:
> Kalle, when I switch from
>
> configuration.add(factory.createChain("/timesheet/**").add(factory.authc()).build());
> to
> @RequiresUser
> private class TimeSheet {
> The issue goes away. Am I do something wrong with my configuration?
>
I
Kalle, when I switch from
configuration.add(factory.createChain("/timesheet/**").add(factory.authc()).build());
to
@RequiresUser
private class TimeSheet {
The issue goes away. Am I do something wrong with my configuration?
Here's my complete config.
public static void
contributeSecurityCo
Hi,
I now found time to sum up a short report about that topic.
I summarized my results in following pdf file:
http://www.schmelzer.cc/Downloads/Files/Tapestry-Memory-Performance.pdf
The main issue is, that you are able to bring a Tapestry based system
into a situation where it gets slower and
I am trying to upgrade from tapestry 4.0.1 to tapestry 4.1.6. In tapestry
4.0.1, for object Ipage we had a function setProperty(String, Throwable)
but it does not exist in Ipage object in tapestry 4.1.6. Please let me know
whether the function is deprecated or do we have any alternate function to
u
