I am currently setting up a survey for our company and have run into a
problem with exceeding my read and write operations in the Google app
engine. Looking at the dashboard I have hit my limit in terms of Datastore
Write Operations (50k per day). How is this value calculated and what does
it represent in terms of ODK data usage (one write operation per
question?). I have been deleting and uploading a couple of new forms today
but have had very little traffic. My survey consists of +- 122 questions
depending on the answers given. Is this a problem other ODK users have
encountered?
The app engine appears to be the easiest way to deploy ODK in the "field",
how are other users managing their surveys and resulting data?
Should we consider moving from a free app engine account to a paid billing
system? Our users are based in Zambia so accessing and uploading completed
surveys via the net is critical.
Many thanks for your time and looking forward to your inputs.
I have had this same situation without even submitting any surveys. Keen to
know why.
···
On Sep 17, 2012 1:47 PM, "Wes Roberts" wrote:
Dear ODK users,
I am currently setting up a survey for our company and have run into a
problem with exceeding my read and write operations in the Google app
engine. Looking at the dashboard I have hit my limit in terms of Datastore
Write Operations (50k per day). How is this value calculated and what does
it represent in terms of ODK data usage (one write operation per
question?). I have been deleting and uploading a couple of new forms today
but have had very little traffic. My survey consists of +- 122 questions
depending on the answers given. Is this a problem other ODK users have
encountered?
The app engine appears to be the easiest way to deploy ODK in the "field",
how are other users managing their surveys and resulting data?
Should we consider moving from a free app engine account to a paid billing
system? Our users are based in Zambia so accessing and uploading completed
surveys via the net is critical.
Many thanks for your time and looking forward to your inputs.
Thanks for the update and the link. I will read it carefully.
How does one update the Aggregate version on the app engine? Should I setup
a new app instance or can I update the software currently running. If you
have link to a how to that would be great. alternatively I will explore
myself.
Regards,
Wesley
···
On Monday, September 17, 2012 1:57:13 PM UTC+2, Yaw Anokwa wrote:
>
> First, make sure you are running the latest version of Aggregate.
> There were quota issues in earlier (generally 1.0.x) releases. Second,
> read http://opendatakit.org/use/aggregate/deployment-planning. If you
> are hitting the quota, switching to a paid plan is a good idea.
>
> On Mon, Sep 17, 2012 at 7:53 AM, Bashir Jahed <ad...@osilab.net> wrote:
> > I have had this same situation without even submitting any surveys. Keen
> to
> > know why.
> >
> > On Sep 17, 2012 1:47 PM, "Wes Roberts" <jwesr...@gmail.com > wrote:
> >>
> >> Dear ODK users,
> >>
> >> I am currently setting up a survey for our company and have run into a
> >> problem with exceeding my read and write operations in the Google app
> >> engine. Looking at the dashboard I have hit my limit in terms of
> Datastore
> >> Write Operations (50k per day). How is this value calculated and what
> does
> >> it represent in terms of ODK data usage (one write operation per
> question?).
> >> I have been deleting and uploading a couple of new forms today but have
> had
> >> very little traffic. My survey consists of +- 122 questions depending
> on the
> >> answers given. Is this a problem other ODK users have encountered?
> >>
> >> The app engine appears to be the easiest way to deploy ODK in the
> "field",
> >> how are other users managing their surveys and resulting data?
> >>
> >> Should we consider moving from a free app engine account to a paid
> billing
> >> system? Our users are based in Zambia so accessing and uploading
> completed
> >> surveys via the net is critical.
> >>
> >> Many thanks for your time and looking forward to your inputs.
> >>
> >> Regards,
> >> Wesley
> >>
> >> --
> >> Post: opend...@googlegroups.com
> >> Unsubscribe: opendatakit...@googlegroups.com
> >> Options: http://groups.google.com/group/opendatakit?hl=en
> >
> > --
> > Post: opend...@googlegroups.com
> > Unsubscribe: opendatakit...@googlegroups.com
> > Options: http://groups.google.com/group/opendatakit?hl=en
>
First, make sure you are running the latest version of Aggregate.
There were quota issues in earlier (generally 1.0.x) releases. Second,
read http://opendatakit.org/use/aggregate/deployment-planning. If you
are hitting the quota, switching to a paid plan is a good idea.
···
On Mon, Sep 17, 2012 at 7:53 AM, Bashir Jahed wrote:
> I have had this same situation without even submitting any surveys. Keen to
> know why.
>
> On Sep 17, 2012 1:47 PM, "Wes Roberts" wrote:
>>
>> Dear ODK users,
>>
>> I am currently setting up a survey for our company and have run into a
>> problem with exceeding my read and write operations in the Google app
>> engine. Looking at the dashboard I have hit my limit in terms of Datastore
>> Write Operations (50k per day). How is this value calculated and what does
>> it represent in terms of ODK data usage (one write operation per question?).
>> I have been deleting and uploading a couple of new forms today but have had
>> very little traffic. My survey consists of +- 122 questions depending on the
>> answers given. Is this a problem other ODK users have encountered?
>>
>> The app engine appears to be the easiest way to deploy ODK in the "field",
>> how are other users managing their surveys and resulting data?
>>
>> Should we consider moving from a free app engine account to a paid billing
>> system? Our users are based in Zambia so accessing and uploading completed
>> surveys via the net is critical.
>>
>> Many thanks for your time and looking forward to your inputs.
>>
>> Regards,
>> Wesley
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
http://code.google.com/p/opendatakit/wiki/AggregateReleaseNotes has
information on how to upgrade from one version to the other. In
general, you can just push the new version to GAE and it'll work just
fine. If you are running an active data collection campaign, you might
want to inform your enumerators of potential downtime (or setup a new
instance).
Yaw
···
On Mon, Sep 17, 2012 at 8:22 AM, Wes Roberts wrote:
> Hi Yaw
>
> Thanks for the update and the link. I will read it carefully.
>
> How does one update the Aggregate version on the app engine? Should I setup
> a new app instance or can I update the software currently running. If you
> have link to a how to that would be great. alternatively I will explore
> myself.
>
> Regards,
> Wesley
>
>
> On Monday, September 17, 2012 1:57:13 PM UTC+2, Yaw Anokwa wrote:
>>
>> First, make sure you are running the latest version of Aggregate.
>> There were quota issues in earlier (generally 1.0.x) releases. Second,
>> read http://opendatakit.org/use/aggregate/deployment-planning. If you
>> are hitting the quota, switching to a paid plan is a good idea.
>>
>> On Mon, Sep 17, 2012 at 7:53 AM, Bashir Jahed wrote:
>> > I have had this same situation without even submitting any surveys. Keen
>> > to
>> > know why.
>> >
>> > On Sep 17, 2012 1:47 PM, "Wes Roberts" wrote:
>> >>
>> >> Dear ODK users,
>> >>
>> >> I am currently setting up a survey for our company and have run into a
>> >> problem with exceeding my read and write operations in the Google app
>> >> engine. Looking at the dashboard I have hit my limit in terms of
>> >> Datastore
>> >> Write Operations (50k per day). How is this value calculated and what
>> >> does
>> >> it represent in terms of ODK data usage (one write operation per
>> >> question?).
>> >> I have been deleting and uploading a couple of new forms today but have
>> >> had
>> >> very little traffic. My survey consists of +- 122 questions depending
>> >> on the
>> >> answers given. Is this a problem other ODK users have encountered?
>> >>
>> >> The app engine appears to be the easiest way to deploy ODK in the
>> >> "field",
>> >> how are other users managing their surveys and resulting data?
>> >>
>> >> Should we consider moving from a free app engine account to a paid
>> >> billing
>> >> system? Our users are based in Zambia so accessing and uploading
>> >> completed
>> >> surveys via the net is critical.
>> >>
>> >> Many thanks for your time and looking forward to your inputs.
>> >>
>> >> Regards,
>> >> Wesley
>> >>
>> >> --
>> >> Post: opend...@googlegroups.com
>> >> Unsubscribe: opendatakit...@googlegroups.com
>> >> Options: http://groups.google.com/group/opendatakit?hl=en
>> >
>> > --
>> > Post: opend...@googlegroups.com
>> > Unsubscribe: opendatakit...@googlegroups.com
>> > Options: http://groups.google.com/group/opendatakit?hl=en
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
Note that there are many reasons why you might get the "Your application
may have exceeded..." screen. You need to look at your billing info, and
see if you have exceeded it.
If not, look in the Logs and see what the reported error is.
Keep in mind that deleting a form definition also deletes each submission
under that form.
Deleting (or uploading) each submission generally costs 1 write operation,
plus 3 or more writes for each media capture (audio, video, image), plus 1
or more writes for each multiple-choice field in the form. If you have 100
submissions with many multiple-choice values, this can quickly add up.
Uploading new form definitions, and deleting form definitions (just the
form definition -- not the associated submissions) can also chew through
your write operations very rapidly. Every question and group in the form
consumes 1 write operation. Simply uploading a 122-question form
definition would incur over 122 write operations.
Mitch
···
On Mon, Sep 17, 2012 at 6:24 AM, Wes Roberts wrote:
Thanks Yaw,
We are currently still developing our surveys and getting to know both ODK
and GAE. Will upgrade when I once again get access to the app.spot.
Reading the link you sent earlier I think our organisation will be
registering for billing, we are far too small to manage our own tomcat
server. Perhaps later this may be an option.
Many thanks for your input,
Wes
On Monday, September 17, 2012 2:48:10 PM UTC+2, Yaw Anokwa wrote:
Thanks for the update and the link. I will read it carefully.
How does one update the Aggregate version on the app engine? Should I
setup
a new app instance or can I update the software currently running. If
you
have link to a how to that would be great. alternatively I will explore
myself.
Regards,
Wesley
On Monday, September 17, 2012 1:57:13 PM UTC+2, Yaw Anokwa wrote:
I am currently setting up a survey for our company and have run
into a
problem with exceeding my read and write operations in the Google
app
engine. Looking at the dashboard I have hit my limit in terms of
Datastore
Write Operations (50k per day). How is this value calculated and
what
does
it represent in terms of ODK data usage (one write operation per
question?).
I have been deleting and uploading a couple of new forms today but
have
had
very little traffic. My survey consists of +- 122 questions
depending
on the
answers given. Is this a problem other ODK users have encountered?
The app engine appears to be the easiest way to deploy ODK in the
"field",
how are other users managing their surveys and resulting data?
Should we consider moving from a free app engine account to a paid
billing
system? Our users are based in Zambia so accessing and uploading
completed
surveys via the net is critical.
Many thanks for your time and looking forward to your inputs.
That explains a lot. I deleted a number of forms before the limit was
exceeded. I now see that I must manage my usage! I will see what I can do
in terms of validating the xml forms and uploading them to an ODK collect
emulator instead of using the app engine to run my tests. I seem to
remember an emulator being available but only on windows. I use Ubuntu
Linux so will see if I can get the emulator to run through wine. I believe
I can also copy the forms directly to the ODK install on my smartphone.
Will explore the options tomorrow.
Many thanks for the helpful information.
Wes
···
On Monday, September 17, 2012 7:27:29 PM UTC+2, Mitch wrote:
>
> Note that there are many reasons why you might get the "Your application
> may have exceeded..." screen. You need to look at your billing info, and
> see if you have exceeded it.
>
> If not, look in the Logs and see what the reported error is.
>
> Keep in mind that deleting a form definition also deletes each submission
> under that form.
>
> Deleting (or uploading) each submission generally costs 1 write operation,
> plus 3 or more writes for each media capture (audio, video, image), plus 1
> or more writes for each multiple-choice field in the form. If you have 100
> submissions with many multiple-choice values, this can quickly add up.
>
> Uploading new form definitions, and deleting form definitions (just the
> form definition -- not the associated submissions) can also chew through
> your write operations very rapidly. Every question and group in the form
> consumes 1 write operation. Simply uploading a 122-question form
> definition would incur over 122 write operations.
>
> Mitch
>
> On Mon, Sep 17, 2012 at 6:24 AM, Wes Roberts <jwesr...@gmail.com wrote:
>
>> Thanks Yaw,
>>
>> We are currently still developing our surveys and getting to know both
>> ODK and GAE. Will upgrade when I once again get access to the app.spot.
>>
>> Reading the link you sent earlier I think our organisation will be
>> registering for billing, we are far too small to manage our own tomcat
>> server. Perhaps later this may be an option.
>>
>> Many thanks for your input,
>>
>> Wes
>>
>>
>> On Monday, September 17, 2012 2:48:10 PM UTC+2, Yaw Anokwa wrote:
>>
>>> Wes,
>>>
>>> http://code.google.com/p/**opendatakit/wiki/**AggregateReleaseNoteshas
>>> information on how to upgrade from one version to the other. In
>>> general, you can just push the new version to GAE and it'll work just
>>> fine. If you are running an active data collection campaign, you might
>>> want to inform your enumerators of potential downtime (or setup a new
>>> instance).
>>>
>>> Yaw
>>>
>>> On Mon, Sep 17, 2012 at 8:22 AM, Wes Roberts wrote:
>>> > Hi Yaw
>>> >
>>> > Thanks for the update and the link. I will read it carefully.
>>> >
>>> > How does one update the Aggregate version on the app engine? Should I
>>> setup
>>> > a new app instance or can I update the software currently running. If
>>> you
>>> > have link to a how to that would be great. alternatively I will
>>> explore
>>> > myself.
>>> >
>>> > Regards,
>>> > Wesley
>>> >
>>> >
>>> > On Monday, September 17, 2012 1:57:13 PM UTC+2, Yaw Anokwa wrote:
>>> >>
>>> >> First, make sure you are running the latest version of Aggregate.
>>> >> There were quota issues in earlier (generally 1.0.x) releases.
>>> Second,
>>> >> read http://opendatakit.org/use/**aggregate/deployment-planning.
>>> If you
>>> >> are hitting the quota, switching to a paid plan is a good idea.
>>> >>
>>> >> On Mon, Sep 17, 2012 at 7:53 AM, Bashir Jahed wrote:
>>> >> > I have had this same situation without even submitting any surveys.
>>> Keen
>>> >> > to
>>> >> > know why.
>>> >> >
>>> >> > On Sep 17, 2012 1:47 PM, "Wes Roberts" wrote:
>>> >> >>
>>> >> >> Dear ODK users,
>>> >> >>
>>> >> >> I am currently setting up a survey for our company and have run
>>> into a
>>> >> >> problem with exceeding my read and write operations in the Google
>>> app
>>> >> >> engine. Looking at the dashboard I have hit my limit in terms of
>>> >> >> Datastore
>>> >> >> Write Operations (50k per day). How is this value calculated and
>>> what
>>> >> >> does
>>> >> >> it represent in terms of ODK data usage (one write operation per
>>> >> >> question?).
>>> >> >> I have been deleting and uploading a couple of new forms today but
>>> have
>>> >> >> had
>>> >> >> very little traffic. My survey consists of +- 122 questions
>>> depending
>>> >> >> on the
>>> >> >> answers given. Is this a problem other ODK users have encountered?
>>> >> >>
>>> >> >> The app engine appears to be the easiest way to deploy ODK in the
>>> >> >> "field",
>>> >> >> how are other users managing their surveys and resulting data?
>>> >> >>
>>> >> >> Should we consider moving from a free app engine account to a paid
>>> >> >> billing
>>> >> >> system? Our users are based in Zambia so accessing and uploading
>>> >> >> completed
>>> >> >> surveys via the net is critical.
>>> >> >>
>>> >> >> Many thanks for your time and looking forward to your inputs.
>>> >> >>
>>> >> >> Regards,
>>> >> >> Wesley
>>> >> >>
>>> >> >> --
>>> >> >> Post: opend...@googlegroups.com
>>> >> >> Unsubscribe: opendatakit...@googlegroups.**com
>>> >> >> Options: http://groups.google.com/**group/opendatakit?hl=en
>>> >> >
>>> >> > --
>>> >> > Post: opend...@googlegroups.com
>>> >> > Unsubscribe: opendatakit...@googlegroups.**com
>>> >> > Options: http://groups.google.com/**group/opendatakit?hl=en
>>> >
>>> > --
>>> > Post: opend...@googlegroups.com
>>> > Unsubscribe: opendatakit...@**googlegroups.com
>>> > Options: http://groups.google.com/**group/opendatakit?hl=en
>>>
>> --
>> Post: opend...@googlegroups.com
>> Unsubscribe: opendatakit...@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
>
I'm having the same problem. I've just set up a new deployment using Aggregate 1.2 and when I go to upload a very simple form from ODK build I get the following error message:
A problem has occurred that prevents your AppEngine application from responding. Your application may have exceeded its per-minute or daily usage quotas.
Please visit your application dashboard at Google AppEngine. The Billing Statussection will indicate what daily or per-minute usage limits your application has exceeded.
If your application's usage limits have not been exceeded, then look for performance issues within Google AppEngine cloud services. From your application dashboard, click on the the System Status link on the left sidebar under the Resources heading. This will report problems with Google AppEngine cloud services.
If neither of those indicate any problems, then your application's Logs may; these are reachable from the dashboard via the Logs link on the left sidebar under the Main heading.
···
On 17 Sep 2012, at 14:56, Yaw Anokwa wrote:
First, make sure you are running the latest version of Aggregate.
There were quota issues in earlier (generally 1.0.x) releases. Second,
read http://opendatakit.org/use/aggregate/deployment-planning. If you
are hitting the quota, switching to a paid plan is a good idea.
On Mon, Sep 17, 2012 at 7:53 AM, Bashir Jahed admin@osilab.net wrote:
I have had this same situation without even submitting any surveys. Keen to
know why.
I am currently setting up a survey for our company and have run into a
problem with exceeding my read and write operations in the Google app
engine. Looking at the dashboard I have hit my limit in terms of Datastore
Write Operations (50k per day). How is this value calculated and what does
it represent in terms of ODK data usage (one write operation per question?).
I have been deleting and uploading a couple of new forms today but have had
very little traffic. My survey consists of +- 122 questions depending on the
answers given. Is this a problem other ODK users have encountered?
The app engine appears to be the easiest way to deploy ODK in the "field",
how are other users managing their surveys and resulting data?
Should we consider moving from a free app engine account to a paid billing
system? Our users are based in Zambia so accessing and uploading completed
surveys via the net is critical.
Many thanks for your time and looking forward to your inputs.