I'll keep looking, but it's weird because that app was consistently
within 1 penny day-to-day before, and its consistently within 1 penny
day-to-day now - it's just exactly double the overall cost...
j
On Oct 18, 2:46 pm, Alfred Fuller
wrote:
> There is no difference between M/S and HRD with reg
I believe the tool is still in Trusted Tester phase.
j
On Oct 18, 6:01 pm, Will wrote:
> Jason,
>
> Where is the automatic migration tool? I looked all places but
> couldn't find it. Is it the "Copy to Another App" button on the
> "Datastore Admin" page?
>
> Thanks,
>
> Will
>
> On Tue, Oct 18, 2
This is making me crazy. I just cannot find the difference in the apps
(M-S vs HRD). The traffic patterns appear to be the same. The total
number of entities is very similar.
When I migrated from M-S to HRD:
- Using the current billing, the app went from $0.00 / day to $1.19 /
day.
- Using futu
I didn´t know it was just to testers. I have sent the mail when they
offer it to test and I have migrated my app to HRD too. Great tool.
Only blobs from blostore were not migrated, but i could move around
this problem.
On 19 out, 15:54, Jason Collins wrote:
> I believe the tool is still in Trus
My datastore writes comparison (0.72M/day to 1.45M/day) is using data
all from the "new pricing" portion.
Somehow, my datastore writes doubled precisely on the day that I
migrated to HRD. My new pricing costs correspondingly doubled from
$0.67 to $1.40.
While there may be no difference in the num
The old app is disabled.
It's tough to compare the load because the dashboard is long since
emptied on the old app. However, the number of Front-end Instance
Hours is effectively the same between old app and new app: around 24
instance-hours.
So we have:
- migration via automated migration tool
I agree Jeff, it really seems this way.
Via the console, I don't see any difference in the indexes, however,
I'm not sure what's going on under the hood. I'm hoping that someone
at Google can look for me?
I imagine I can use the cost on the RPCs (a la https://gist.github.com/715284)
to see if the
Jason,
You said that you deployed the same code to the HRD instance of your app
that was running on the Master/Slave instance. Is there any part of your
application that might behave differently in the face of HRD's slightly
different read consistency guarantees? Are you ever writing data and t
Different theory:
It looks like your cron jobs are still running in your old app. Could you
please try redeploying an empty cron config for your old app and let me
know when you've done that?
Thanks,
Max
--
You received this message because you are subscribed to the Google Groups
"Google App
The old app is disabled. Would the crons still be running?
On Oct 28, 1:29 am, "Max Ross (Google)" wrote:
> Different theory:
>
> It looks like your cron jobs are still running in your old app. Could you
> please try redeploying an empty cron config for your old app and let me
> know when you've
Wow. So it _does_ look like the old crons were running even though the
application was DISABLED. This will likely bite other users of the
automated migration tool. You might want to address this. Note that
Ikai suggested this long ago, and I just assumed that a disabled app
would not be running cro
Cron jobs should not be running on a disabled app. We'll fix it.
Please do let us know if your datastore writes return to their original
levels.
Thanks,
Max
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the w
Thanks all. The billing has come through now, and everything has
dropped right back to its original levels.
j
On Oct 28, 9:20 am, "Max Ross (Google)" wrote:
> Cron jobs should not be running on a disabled app. We'll fix it.
>
> Please do let us know if your datastore writes return to their origin
That's great to hear, thanks for being so patient with us while we sorted
this out.
Max
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/e9vpwXrIX
I see that I never responded to Max here.
Yes, once my old crons were disabled, everything returned to normal.
Thanks,
j
On Oct 28, 10:20 am, "Max Ross (Google)" wrote:
> Cron jobs should not be running on a disabled app. We'll fix it.
>
> Please do let us know if your datastore writes return t
Wait, are you comparing the old pricing model or the new pricing model
(since you attributed the cost to writes I just assumed you were talking
about the new pricing model)? In the old pricing model HRD writes cost more
(~3x).
On Fri, Oct 21, 2011 at 8:18 AM, Jason Collins wrote:
> This is making
He seems to be comparing the number of writes:
- Datastore writes went from 0.72M / day to 1.45M / day
>
This is the new model isn't it?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://g
Long shot ... any chance your old app is still running? If so, could task
queues/cron jobs on the old app might be hitting the new app and causing an
increase in writes? Of course ... you would see additional load if this were
the case.
This would be much easier to solve if we knew which handlers
I really have to wonder if somehow you've added extra indexes during the
migration. That could easily cause this doubling. In the absence of any
business logic changes, this is what I would focus my investigation on
first.
Jeff
On Tue, Oct 25, 2011 at 8:27 AM, Jason Collins wrote:
> The old ap
Keep in mind that the console only shows you multi-property indexes defined
in yaml/xml. It doesn't show single-property indexes, which can be
configured on an entity-by-entity basis.
Jeff
On Tue, Oct 25, 2011 at 1:28 PM, Jason Collins wrote:
> I agree Jeff, it really seems this way.
>
> Via th
Thanks for getting to the bottom of this, Jason. You're right: the cron jobs
should not run on a disabled app. We'll fix this.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com | twitter.com/ikai
On Fri, Oct 28, 2011 at 9:13 AM, Jason Collins wrote:
> Wow. So it _does
21 matches
Mail list logo
