Query performance depends on the amount of entities returned for a given query and how big each entity is. It's independent of the total dataset size. If users are fetching the same data, you can cache it. If entities are typically returned together, you can build another entity containing all the data for one query (for example, today's top-10 blog posts) so you only return one entity.
You can use up many instances serving 100 users or you can use one instance serving those users - depends entirely on how well you write the app. So start writing a test app that fetches a few entities and get a handle on how the datastore operates, and how to improve performance. On Tuesday, April 10, 2012 4:10:53 AM UTC+2, didinj wrote: > > In case I have entity contains 20 fields and 1million record accessed by > 100 users at the same time to put and get 1 record of each. How to > calculate it? > Pada 10 Apr 2012 02.43, "Richard Watson" menulis: > >> Depends on various things. How you've structured your data, how >> efficiently you serve it, how many users, etc. >> >> On Monday, April 9, 2012 2:24:16 AM UTC+2, didinj wrote: >>> >>> Hi all, >>> >>> How to calculate instance hours? is that depends on how many users >>> accessing the apps? >>> >>> Thanks, >>> Didin >>> >> -- 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/-/780iGp2SSEYJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
