[
https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091422#comment-13091422
]
Robert Zeigler commented on TAP5-1616:
--------------------------------------
#1) I guess that's personal preference. I usually don't like my applications
consuming more memory than they need to, even if I have the resource budget for
it. :) In particular, I've worked in many resource-constrained environments
where there are multiple web apps running off the same servlet container so
that even though the container has a reasonable amount of memory allocated to
it, each app has to "play nice" within that environment to avoid hogging the
RAM. Buy more RAM? Build another server? Yes, I agree. But we're not always
the ones who get to make those decisions. So I appreciate being able to
explicitly tune things like how long pages stay in memory.
2) I suppose. But I do think it's nice to be able to tune that for
performance. There's a time/memory trade-off when releasing pages due to the
cost of recreating them. Servers where the application doesn't get used much
but the server is housing other apps (eg: small-ish in-house-style apps) would
probably want a quicker unload time to leave more memory resources available
for other applications. High traffic sites probably want pages to reside in
memory a longer time.
> PeriodicExecutor service prevents running T5.3 on GAE
> -----------------------------------------------------
>
> Key: TAP5-1616
> URL: https://issues.apache.org/jira/browse/TAP5-1616
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Kalle Korhonen
>
> Since GAE doesn't allow user-created threads, constructing PeriodicExecutor
> service fails on GAE, preventing running the whole application on it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
