diff --git a/docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc b/docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc
index a15f96126..96ccb3436 100644
--- a/docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc
+++ b/docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc
@@ -98,7 +98,18 @@ that don't contain a results field are not included in the {reganalysis}.
 === {classification-cap} field types
 
 {classification-cap} supports fields that have numeric, boolean, text, keyword, 
-or ip data types. It is also tolerant of missing values. Fields that are supported are 
-included in the analysis, other fields are ignored. Documents where included 
-fields contain an array are also ignored. Documents in the destination index 
-that don't contain a results field are not included in the {classanalysis}.
+or ip data types. It is also tolerant of missing values. Fields that are 
+supported are included in the analysis, other fields are ignored. Documents 
+where included fields contain an array are also ignored. Documents in the 
+destination index that don't contain a results field are not included in the 
+{classanalysis}.
+
+[float]
+[[dfa-inference-nested-limitation]]
+=== Deeply nested objects affect {infer} performance
+
+If the data that you run inference against contains documents that have a series 
+of combinations of dot delimited and nested fields (for example: 
+`{"a.b": "c", "a": {"b": "c"},...}`), the performance of the operation might be 
+slightly slower. Consider using as simple mapping as possible for the best 
+performance profile.