Storage engine esent and voron

[Jason.W He]

Just curious about current state on RavenDB 3.5. Esent and voron which one is prefered engine in v3.5. As 4.0 will be purely voron, but not sure if we should target voron for any new databases.

I know it might be personal preference, but as of use esent for past 3~4 years, there was issues with esent version, memory exception etc. I know voron is in place to resolve that, but I'm not sure about state of current voron engine. What's pro and cons when switch to voron from esent?

If voron is better option are there anyway to switch existing database to voron?

[Oren Eini (Ayende Rahien)]

Voron is stable and is used in production, it tend to have lower cost for running than Esent, and faster overall, and doesn't suffer from the OS tie limitation.

Esent is what we used for a long time, and it is the current default for 3.x because it is the known option.

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

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

[Jason.W He]

Thanks for explain. 

For exisint database, are there anyway to switch to use voron other than export and import? When upgrade to v4.0 in the future, will database automatically convert old database to voron from esent?

[Oren Eini (Ayende Rahien)]

No, there is no way outside of export / import.

For 4.0, the db will handle that part for you, but it will still be doing export/ import, most likely.

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

On Wed, Nov 9, 2016 at 10:23 PM, Jason.W He <hekyl...@gmail.com> wrote:

Thanks for explain. 

For exisint database, are there anyway to switch to use voron other than export and import? When upgrade to v4.0 in the future, will database automatically convert old database to voron from esent?

--