English to French Tech/Engineering Computers: Systems, Networks A strategy used to scale on GAE

This article was written by an American , and in this particular context I'm not sure if he means 'sauvegarder' or 'ralentir', 'faire un embouteillage'.

7. Split a table into two parts: main model and an additional info model. Datastore puts are your largest cost so you need to do everything you can to minimize their cost. In the main model use keyed access only, no indexes, and keep no extra fields. Gets will be fast and puts will be cheap. Writing extra fields costs time and money. So a “date joined” field for a User model doesn't belong in the main table. It isn't used often so put this kind of data in an additional info model. Put your indexes on this model and perform queries against it. Because the additional info model has indexes it will cause more synchronized writes which costs more, is slower, and can BACK UP processing if you need to write this model frequently.