Re: [google-appengine] Where to store thousands of Constants?

On Thu, Jun 9, 2016 at 6:50 PM, YuRen Lin wrote: > Hi, Nicholas > > Thanks for your explanation. Very nice. I think the most simple and > fastest way is to store all these constants in resource file and then load > them to instance memory. Do you know how much instance memory

Re: [google-appengine] Where to store thousands of Constants?

Hi, Nicholas Thanks for your explanation. Very nice. I think the most simple and fastest way is to store all these constants in resource file and then load them to instance memory. Do you know how much instance memory a Java App Engine can hold? 'Nicholas (Google Cloud Support)' via Google App

Re: [google-appengine] Where to store thousands of Constants?

Hi, Jeff. Do you mean load all of them into "instance memory"? I am not sure how much instance memory I have in app engine. That should work, but need to measure the startup time of instances. When a lot of requests come in, each instance has to keep these copy of constants in their instance

Re: [google-appengine] Where to store thousands of Constants?

Just a few thousand constants? Even if each was 1k (!), you’re talking about a few megabytes of RAM. Why not just load them from CSV into RAM and keep them there? Jeff On Wed, Jun 8, 2016 at 8:20 PM, YuRen Lin wrote: > Hi, all > > I am in the game industry and use Google

[google-appengine] Re: Where to store thousands of Constants?

Thanks for sharing your question and situation here. >From what I understand of your scenario, accessing a large array of integers from memcache and occasionally Datastore is not quite as fast as is needed for your implementation. The fastest as you suggested would be to have all constants

Re: [google-appengine] Re: Endpoint User Authentication

It appears the user was using the wrong code to get a User object. In Java Endpoints, the User object is passed as a parameter to the @ApiMethod -annotated method . Could you

[google-appengine] Re: Stackdriver Debugger for flexible environment

This is a known issue and we're working on fixing it. On Thursday, June 9, 2016 at 9:33:31 AM UTC-7, Amaury Gauthier wrote: > > Hello, > > On this page > we > can read: > >> Stackdriver Debugger is enabled automatically

[google-appengine] Re: Where to store thousands of Constants?

One approach that can work really is to store this data as a json document in google cloud storage. This may require architectural changes however for the client to get the information. On Wednesday, June 8, 2016 at 10:20:03 PM UTC-5, YuRen Lin wrote: > > Hi, all > > I am in the game industry

[google-appengine] Stackdriver Debugger for flexible environment

Hello, On this page we can read: > Stackdriver Debugger is enabled automatically for Python applications > running in the Google App Engine standard >

[google-appengine] AppEngine with Endpoints

>From the tutorials I have seen, you can package html/css within an Endpoints app, effectively creating a dynamic web app. Is this good practise, or is the recommended approach to create a separate app (containing the front-end code) and host it in app engine? -- You received this message

[google-appengine] Prova

prova -- 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...@googlegroups.com. To post to this group, send email to

[google-appengine] Re: Google AppEngine blocked by MailChimp because of security issues

I think a virtual_ip feature might be nice for these kind of problems, you could buy IP's, and add them as an argument to .fetch calls like .fetch(virtual_ip="1.2.3.4") etc. - As a lot of people are experiencing similar issues, mainly while fetching url's Other than this idea, let's hope they

Re: [google-appengine] Re: project with python and node services: inconsistent data

Hi Faried, Try deleting the Memcache key which is used by NDB after you update the Datastore entity on the Node server (FYI, NDB Memcache implementation found here ). Something like this (NOTE:

[google-appengine] Re: project with python and node services: inconsistent data

On Thursday, June 9, 2016 at 12:36:09 AM UTC+5, Christian F. Howes wrote: > > Does your node service use NDB or DB? if it is using NDB then NDB takes > care of flushing the cache for you when you update an object, but you have > to `get_by_key` in order to get the latest copy. > NDB is a

Re: [google-appengine] Re: project with python and node services: inconsistent data

On Wednesday, June 8, 2016 at 11:53:00 PM UTC+5, Nick (Cloud Platform Support) wrote: > I suggest replacing your "get" query with a "get-by-key" query to force > strong consistency. > Where is this "get-by-key" or "get_by_key" query documented? I can't find any references to it in the

[google-appengine] Re: Where to store thousands of Constants?

We also use App Engine for our game content, and in our case, all our game data is just stored in Python modules. In 'code' as you will. An advantage of this is that you can easily send game data back just from instance memory. For us the increase in startup time is negligible, although I do