Raven/Esent/MaxVerPages <-- what does this mean?

590 views
Skip to first unread message

Justin A

unread,
May 9, 2013, 10:54:34 PM5/9/13
to rav...@googlegroups.com
Ok - the official docs say:

Raven/Esent/MaxVerPages
The maximum size of version store (in memory modified data) available. The value is in megabytes. 
Default: 512

Does this mean to a blond person like me, that if i want to update an existing document, the document(s) size in total, (both before AND after the change because I'm assuming change tracking keeps track of both states, to some degree) can't exceed 512MB (by default).

So if i load in a document that has a massive WKT (shoot me, please) which is around 250-300MB in size and then i decide to update this WKT shape .. then i'm going to havr around 600MB in memory now .. and boom - Out Of Memory exception (eg. ravendb version store out of memory)

is that more or less it?

2ndly, can we change this value on the fly, programatically? eg. i know i'm about to store a massive doc so ... lets change this settings-value .. store.savechanges. revert-change this settings-value back to 512.

-J-

Oren Eini (Ayende Rahien)

unread,
May 10, 2013, 1:18:01 AM5/10/13
to ravendb
Justin,
You are pretty much correct, yes. Note that this memory is shared, and it is important that you will have enough for ALL concurrent operations in the db.
If you have documents that large, RavenDB is going to need a lot more ver pages.
Please note that documents in that size are supported, in the sense that it will work, but it is going to be very expensive.

And you need to set it when the db is initialized.



-J-

--
You received this message because you are subscribed to the Google Groups "ravendb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Justin A

unread,
May 10, 2013, 1:51:39 AM5/10/13
to rav...@googlegroups.com
Thanks Oren!

I know this touches on the recently asked question "Maximum recommended document size" .. but if we have large Well Known Text shapes which we need to do spatial queries against, we have no choice but to stick them into the db as is, right? And cope the long spatial indexing wait...

(BTW, i ment to say 250K - 300K .. not MB! Oops)

Oren Eini (Ayende Rahien)

unread,
May 10, 2013, 1:54:28 AM5/10/13
to ravendb
Well, yes. Unfortunately.
At least right now. If you have any good ideas about alternatives to that, I would love to hear it.


--
Reply all
Reply to author
Forward
0 new messages