homepage is empty at the moment, you can use
http://www.keepyourappwarm.com/manage
to access management console directly
I will add some explanation / comparison later on
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this disc
While I agree with jeff to a large extent -- you should pay for
hosting rather than gaming it -- I could still see this being useful.
Instead of using it to "warm up" your app, it would be nice to have a
third party performance monitor that could, for example, monitor your
app's uptime, latency, et
Hi Bejayoharen,
Great thanks for the feedback.
As I said this is just several hours work so sorry for the UI. I agree it's
not quite comprehensive.
You can login with your Google Account by clicking top-right link "Log in
with your Google Account to manage your warmers"
You will be able to
It must not be too bad from Google's perspective, as they include an
example of a "recache" job in the GAE java cron documentation:
http://code.google.com/appengine/docs/java/config/cron.html
That said, I'm not sure why anyone would necessarily want to do this,
given the new pricing.
On Jul 11,
Lame.
Whether or not it is against the letter of the law, it's certainly
against the spirit of appengine. If your little "hack" becomes
popular, the likely consequence is that Google will have to devote
resources to engineering (or gaming) around it. I do not approve.
If you need always-on beha
On Sun, Jul 10, 2011 at 5:17 PM, bejayoharen wrote:
>
> A great project would be one that worked from a
> third party site (non-cloud hosting would suffice), checked your site
> periodically, and contacted you (eg sent you a text message using
> twillio) if there was any trouble.
There are o
On Sun, Jul 10, 2011 at 4:26 PM, Barry Hunter wrote:
> On Sun, Jul 10, 2011 at 5:17 PM, bejayoharen wrote:
>>
>> A great project would be one that worked from a
>> third party site (non-cloud hosting would suffice), checked your site
>> periodically, and contacted you (eg sent you a text mes
hi Jeff,
AFAIK, lots of GAE developers are using cron job to *warm up*, including me.
You can search in this group, many ppl are doing this.
Also, if we want something more than a periodic ping, like those use cases
you mentioned, then we probably don't want all these logic stay with in our
Using cron to keep your app warm is not sanctioned either. If Google wanted
to give you a way to keep your app running, they'd offer it as a feature and
charge for it.
If these hacks become commonplace, GAE engineers will be retasked to
fighting them and this will further delay new features that
Hi Jeff,
I believe that with the new pricing that may have already happened. If you
keep your app "warm" with no one using it you're going to be paying for it.
A lot of users will probably want their instances to shutdown faster rather
than stay up and be either billed or use up their free quota.
S
Agree with your point on tragedy of the commons. The thing is this is not a
new concept. It's already a common practice among many appengine developers.
Without my application, one can still write a dummy cron in 5 mins. Given
that they (unfortunately including me at the moment) will do it anyw
Isn't the end of point 4.4 applicable here...
"or otherwise access the Service in a manner intended to avoid incurring
fees"
...as you are avoiding paying the $9/month for an always running instance?
Phil
On 12 July 2011 08:10, Max wrote:
> Agree with your point on tragedy of the commons. The
my understanding is, you can't hack a service for free if it's supposed to
be paid. By using my application, you still use / pay for your normal
instance rather than always on instance. so this term is not applicable to
this case.
--
You received this message because you are subscribed to the
I can't believe I'm still writing about this... at the very least
you're hacking around the $9/mo fee for an always-on instance.
The "free tier" of appengine works because all those zillions of
little test apps and experiments that people create don't actually
occupy resources beyond a small amou
On Tue, Jul 12, 2011 at 1:26 AM, jeffrey_t_b wrote:
> It must not be too bad from Google's perspective, as they include an
> example of a "recache" job in the GAE java cron documentation:
If you are recaching something every 2 minutes, there is a certain
expectation that you going to be needing i
15 matches
Mail list logo
