Update README.md

Author: igdianov

README.md

@@ -320,8 +320,12 @@ of sorting by name for Human objects. The default sort order can be specified us
 
 Performance
 -----------
+Lazy loading of associations between entities is a well established best practice in JPA. Its main goal is to retrieve only the requested entities from the database and load the related entities only if needed. The use of FetchType.EAGER for associations mapping is one of the most common reasons for performance problems, because Hibernate loads eagerly fetched associations when it loads an entity. This is very inefficient and it gets even worse when you consider that Hibernate does that whether or not you will use the associated data.
+
 The JPA DataFetcher implementation will attempt to build dynamic fetch graph in order to optimize query performance and avoid N+1 lazy loading. However, if there are composite foreign keys being used on `@ManyToOne` association declared in GraphQL query, Hibernate persistence provider will issue a separate SQL query to resolve the parent entity.
 
+To disable default `@ManyToOne` associations default behavior of eager fetch, make explicit use of FetchType.LAZY for all to-many associations in your entity model. It will delay the initialization of the relationship unless it is specified in the GraphQL query entity graph to improve performance when fetching many entities with to-one associations.
+
 GraphiQL Browser
 --------