[google-appengine] Large data volume for live reports

HI, I have been using Google app engine for a while and faced some timeout issues while handling large data sets. MY application developed on Java Platform. Problem: When customer selects a date duration from UI, request goes to app engine to fetch the data from data store and run through cus

[google-appengine] Re: Large data volume for live reports

if something is taking longer than 20-30 sec to generate, it is not good to make user to wait. One minute limit for requests is there for a reason. Either you have to prepare document in advance, or use bigquery, or send email once doc is ready. On Sunday, 15 December 2013 11:01:19 UTC, Anil

[google-appengine] Re: Bug in counting datastore small ops?

Hi, again! This is not a bug in counting small quote, this is side effect of Remote API. More I will not use that. :) Thanks all! суббота, 14 декабря 2013 г., 22:32:25 UTC+6 пользователь Lapteuh написал: > > Hi all! > > Recently, I had to remove all entities of a certain type in the datastore.

Re: [google-appengine] APP Engine hosting an iMacros app

Alrright thanks Mr Viny. Le mercredi 4 décembre 2013 02:29:44 UTC, Vinny P a écrit : > > On Tue, Dec 3, 2013 at 11:27 AM, Youssef Naki > > > wrote: > >> because honestly my imacros script i developed within imacro language, i >> don't understand what you mean by what language your code is code

[google-appengine] Re: Large data volume for live reports

Hi! You should probably take a general look at what you are dealing with, and consider some which common options are available. Some of these could apply to your project: 1) Segment data into smaller chunks, and deliver partial data if possible. 2) Have precomputed a summary, if you are summing

[google-appengine] Re: Listen Google: Error code 203

This just happened for my app, python27, SDK 1.8.8 did you ever hear anything back? Is there an issue open for this? Thanks, PK On Saturday, February 16, 2013 12:48:25 AM UTC-8, Deepak Singh wrote: > > Hi, > > Most often i get this error > > The process handling this request unexpectedly died.

[google-appengine] Re: Listen Google: Error code 203

There is already an issue: 9549that I just starred. All 7-8 threads in the instance died like that but noone seemed to reveal an issue. Is this the crude way applications are migrated from one server to another? By the way don't

[google-appengine] Re: Bug in counting datastore small ops?

You didn't mention disabling indexes in your OP. You are using iter over remote api, I usually use big batches (1000) using a cursor for remote_api work. It may be the small iter/small batches create a lot of roundtrips and these would add up as small ops. On Monday, December 16, 2013 1:05:

[google-appengine] Re: Appengine is down (errorcode 104)

Thank you for your reply. The log tells that it is the initialization of a new instance that takes longer than 60 seconds and therefore it is shut down. This means that no new instances could be started causing our service to be completely down. The strange and unanswered part is still that our