All geek questions in one place

Does increasing the number of models in Google App Engine affect performance?

I made the Google App Engine application as a project class at my university. Now I need to optimize it for commercial use.

The code is currently very slow. It has only a few models with many properties. Before rewriting the Model code, I need to know if my application will be faster if I increase the number of models, i.e. Will increase the denouement. And to what point should I consider the separation of models in other models?

Another question is, if decoupling positively affects performance, is the number of properties in the model directly proportional to the time it takes to retrieve from the data warehouse?

+3
source share
1 answer

The code is currently very slow. It has only a few models with many properties in each.

Getting / placing large objects

Since the data warehouse API can only place or receive an object (as opposed to individual fields), every time you select an object for a data warehouse, it retrieves all its fields, regardless of whether you are going to use all of them at this moment or not, This effect will be stronger when we write the object back to the data store, it should write everything, even if you change one field in the object. (writes more than read)

- : .

, , , title, date body ( , ). BlogPost, , titles (, ) dates.

class BlogPost {
String title; String body; long date; }

, , body, body, () BlogPost.

class BlogPost {
String title;
Key<Body> body;
long date;
}

class Body {
String body;
}

BlogPost , , , - ( JavaScript), , GWT.

Google App Engine ?

:

, .

+7

Source: https://habr.com/ru/post/1763524/

More articles:


All Articles