Btw, I also found that tynamo's implementation of JPATransactionManager
doesn't fit well when using DAO-level caching.
Assume I have AccountDAO interface:
public interface AccountDAO {
@CommitAfter
public Account getAccount();
}
AccountDAOImpl is an implementation of this interface that com
On Mon, Jun 7, 2010 at 20:38, Howard Lewis Ship wrote:
> That's interesting, that GAE shuts down your instances.
Yes, its a big issue for some projects, so now google is working to
impoement support for dedicated JVMs:
"The work is in the progress but we should wait for the results. Here
is th
Indeed, if you let the app go cold, you will quickly spend a large amount of
your GAE free quota on starting up the app (in addition to having a really
slow load of the first page).
I have a cron task on a separate box that wget-s the whole site every 3
seconds. This ends up eating up about 20% of
http://www.answercow.com/2010/03/google-app-engine-cold-start-guide-for.html is
an interesting read on how much startup time is spent on several java
libraries at
GAE
On Mon, Jun 7, 2010 at 19:38, Howard Lewis Ship wrote:
> That's interesting, that GAE shuts down your instances. There's a bit of
That's interesting, that GAE shuts down your instances. There's a bit of
Tapestry based on the idea that the application is long running, so it's OK
if it takes a moment to start up initially. Under GAE that's not the case
... perhaps Tapestry under GAE should be even a bit lazier about loading an
