[google-appengine] Appstats for Go versions on appengine production

2013-01-25 Thread Carl Schroeder
I wants. I can has appstats yet? Don't make me find a cat pic for this. ;) -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@goog

[google-appengine] Re: Cost of updating list property

2013-01-25 Thread Kaan Soral
I think all of you except Micheal missed the point of the question. I hate when this happens to me :) Of course it's impossible to store 1 million integers in a list property, however, I think in the question, 1million was more like an N and the point of the question is to whether any update to

[google-appengine] Re: Latency Issues across Production APIs

2013-01-25 Thread Prateek Malhotra
Sorry, forgot to mention: Memcache and Task Queues seem to be the most effected. Tasks that usually take 10-20 seconds on my backends are taking almost 2 minutes. Some tasks seem to not even fully complete. Also, I use memcache as a "synchronizing" mechanism and use incr/decr to keep track of h

[google-appengine] Latency Issues across Production APIs

2013-01-25 Thread Prateek Malhotra
The status dashboard keeps switching between "Elevated" and "Normal" and these graphs show an obvious spike in latency: Memcache Set: HR Datastore Queries:

[google-appengine] the email associated with our app engine account was inadvertently reassigned as a "nickname"

2013-01-25 Thread Piper Davies
we've reassigned the email as its own entity, but are now unable to access our app engine. HELP! thanks so much :) -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an em

[google-appengine] Strange issues on production

2013-01-25 Thread Prateek Malhotra
We have a process that splits a job between backend instances and "synchronizes" via memcache (not the best method, I know, but it has been working for us). Earlier in the day, we started seeing weird behavior. Its one or more of the following: 1. Backends are acting funky 2. Memcache latency/

Re: [google-appengine] Re: Cost of updating list property

2013-01-25 Thread Guido van Rossum
The only way to get this to perform is to serialize the values into a string. Repeated properties are way too slow when you get to this number of repetitions. (They're good for tags, which need to be indexed, and of which youd expect there to be z few, or dozens, or occasionally hundreds.) --Guido

[google-appengine] Re: Cost of updating list property

2013-01-25 Thread Michael Hermus
I believe that each value in an indexed multi-valued property gets its own index entry. Therefore, I think that adding 1 value should incur the cost of adding one index entry, which is 2 writes (one for asc, one for desc) and 1 write for each custom index that includes the property. -- You rec

[google-appengine] Re: Cost of updating list property

2013-01-25 Thread Ryan Chazen
Depends if those integers are indexed or not. Each index is a write op. However, an entity can only be 1mb big.. I think 1 million integers would be more than 1mb as appengine stores natively as strings... What you could try is to store the integers in multiple entities (say 1-1000 integers per

[google-appengine] Cost of updating list property

2013-01-25 Thread Jiansen He
Hi, Say an entity has a list property which has 1 million integers. Now we need to update the list property by adding 1 more integer. Does updating via put cost 2 million write operations? If so, is there a cheap alternative? With Thanks Jiansen -- You received this message because you are

[google-appengine] Re: Strange Memcache put error

2013-01-25 Thread Deepak Singh
Still getting the same issue. Could not find why it throws this error while writing to memcache. On Mon, Jan 21, 2013 at 10:03 PM, Deepak Singh wrote: > Hi All, > > I am getting a strange error as follows > > com.pdstechi.hotel.server.HotelRpcServiceImpl getRoomsXmlHotelSearchResult: > Memcache

Re: [google-appengine] API Search OverQuotaError

2013-01-25 Thread Andreas Schmid
did you index multiple documents simultaneously? i know there is a limit also on how many documents get indexed per second or some other time limit. this is not documented. On Jan 25, 2013, at 9:19 AM, Aza Tek wrote: > On Fri, Jan 25, 2013 at 3:29 PM, Andreas Schmid wrote: > it means you rea

Re: [google-appengine] API Search OverQuotaError

2013-01-25 Thread Aza Tek
On Fri, Jan 25, 2013 at 3:29 PM, Andreas Schmid wrote: > it means you reached the daily limit and have to wait until the quota > resets or request a higher quota. > And the 3% is a percentage of? -- You received this message because you are subscribed to the Google Groups "Google App Engine"

Re: [google-appengine] Terms of service diff

2013-01-25 Thread Joshua Smith
(of course, I meant Nov 2012; still haven't adjusted to this year being 2013 :) On Jan 25, 2013, at 8:51 AM, Joshua Smith wrote: > http://web.archive.org/web/2012073615/https://developers.google.com/appengine/terms > > That's the previous version from Nov 2011. I did a quick diff and almost

Re: [google-appengine] Terms of service diff

2013-01-25 Thread Joshua Smith
http://web.archive.org/web/2012073615/https://developers.google.com/appengine/terms That's the previous version from Nov 2011. I did a quick diff and almost every clause has some changes. You are spitting in the wind asking Google's technical and business people to explain what Google's law

Re: [google-appengine] API Search OverQuotaError

2013-01-25 Thread Andreas Schmid
it means you reached the daily limit and have to wait until the quota resets or request a higher quota. On Jan 25, 2013, at 4:11 AM, Moises Belchin wrote: > Hi all, > > We've getting this error: > > OverQuotaError: The API call search.IndexDocument() required more quota than > is available.

[google-appengine] API call search

2013-01-25 Thread Moises Belchin
We're having many errors like this. *The API call search.Search() took too long to respond and was cancelled.* Does anyone have the same problem? Thanks and regards. Moisés Belchín. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To pos

[google-appengine] API Search OverQuotaError

2013-01-25 Thread Moises Belchin
Hi all, We've getting this error: OverQuotaError: The API call search.IndexDocument() required more quota than is available. However our Search API Quota is about 3% SearchSearch API Calls [image: 3%] 3%149,105 of 4,320,000OkaySearch Stored Data [image: 0%] 0%0.04 of 100.00 GBytesOkay What doe