From 51fede57a203b2f5c5fefa3e69dc580e1851b73f Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Mon, 14 Jun 2021 16:23:41 +0000 Subject: [PATCH] Added a comment --- .../comment_27_db91e10d0bea246686ba2241b348e67d._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/significant_performance_regression_impacting_datal/comment_27_db91e10d0bea246686ba2241b348e67d._comment diff --git a/doc/bugs/significant_performance_regression_impacting_datal/comment_27_db91e10d0bea246686ba2241b348e67d._comment b/doc/bugs/significant_performance_regression_impacting_datal/comment_27_db91e10d0bea246686ba2241b348e67d._comment new file mode 100644 index 0000000000..e1c5cfe399 --- /dev/null +++ b/doc/bugs/significant_performance_regression_impacting_datal/comment_27_db91e10d0bea246686ba2241b348e67d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 27" + date="2021-06-14T16:23:41Z" + content=""" +FWIW, without having a clear idea on code logic/data structures, it smells a bit like somewhere may be it could be `any` vs current `all` operation/check (in case of `add` at least) if needed just to test if there is already a path with a given key, and assuming that DB doesn't require a full rewrite of all `path` entries if a new path added for the key. +"""]]