You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/optimization.adoc
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,18 +2,18 @@
2
2
= Optimization
3
3
4
4
5
-
This chapter contains some optimizations to improve the performance of a production system using `@neo4j/graphql`.
5
+
This page contains optimizations to improve the performance of a production system using `@neo4j/graphql`.
6
6
7
-
== Schema Optimisations
8
-
This section covers improvements to reduce the size of the generated schema. Reducing the schema size has the following performance benefits:
7
+
== Schema optimizations
8
+
This section covers optimizations to reduce the size of the generated schema. Reducing the schema size has the following performance benefits:
9
9
10
-
* Reduce the startup time of the server.
10
+
* Reduce server startup time.
11
11
* Reduce memory footprint.
12
12
13
13
=== Exclude `@deprecated` fields
14
14
The `@neo4j/graphql` library generates some GraphQL fields and operations marked as `@deprecated`. These exists to keep compatibility with previous versions of the library.
15
15
16
-
If you are not using these deprecated fields, you can disable generation for these with the `excludeDeprecatedFields` flag in the library setup.
16
+
If you are not using these deprecated fields, you can disable their generation with the `excludeDeprecatedFields` flag in the library setup.
17
17
18
18
The following example disables all deprecated fields that are generated in the library:
0 commit comments