How does LoadDocument exactly affect an index?
29 views
Skip to first unread message
Pubudu Gunawardena
Jun 15, 2021, 6:10:00 AM6/15/21
to RavenDB - an awesome database
Hi All,
"Using the LoadDocument adds a loaded document to the tracking list. This may cause very expensive calculations to occur, especially when multiple documents are tracking the same document."
But how exactly does that affect indexing performance?
We have an index which has two calls to LoadDocument. One of those documents are rarely updated, whereas two of them are updated somewhat frequently. We had some issues with this index with errors like "Failed to allocate memory, 16GB already allocated to this thread". When we look at this index in the dashboard, the progress bars on the index update process shows all three documents, even though one of the collections are rarely updated. Does this have to do with the above message in the documentation?
How could we improve this index?
meshcloud GmbH
Office +49 (69) 34 87 35 87
Sonnemannstr. 5
60314 Frankfurt am Main
60314 Frankfurt am Main
Germany
Visit our website:
www.meshcloud.io
www.meshcloud.io
Ryan Heath
Jun 15, 2021, 7:41:32 AM6/15/21
to rav...@googlegroups.com
Are those loaded documents the very same documents loaded for each entry in your index?
When one of those docs were updated all the index entries that refer to that doc must be updated too.
When one of those docs were updated all the index entries that refer to that doc must be updated too.
This can be expensive depending on how many index entries and other things you are doing in the index.
// Ryan
--
You received this message because you are subscribed to the Google Groups "RavenDB - an awesome database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/faf2342b-55f6-4c72-8713-159f1c1a9411n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages