Strangest Support Calls for RavenDB
We've gotten some weird report calls for RavenDB on the support line, from OutOfMemoryExceptions to slow startup times.
Join the DZone community and get the full member experience.Join For Free
We have a support hotline for RavenDB, and usually we get people that give us “good” problems to solve. And then we have the people who… don’t.
The following are a few of the strangest issues from the past month or so.
- OutOfMemoryException is thrown when running RavenDB in 32 bits mode, and documents of size of 50-70MB size are used.
Solution – When running in 32 bits mode, RavenDB only have 2GB of virtual memory to work with, and that is really not enough to do much. There is no reason today for any server app to run in 32bits mode. Also, a 70MB document?! Seriously!
- Very slow startup time for RavenDB when the number of indexes approaches 20,000.
Solution – That isn’t a typo, honest. We had a customer that sent us a database that had 19,273 indexes in it. When they restarted the database, we had to load all of those indexes, and that took a… while. And no, those weren’t dynamic indexes, they were static indexes that (I hope, at least) were probably generate by a tool.
- Index creation can take a long time when the number of map indexes in a multi map index is higher than 150.
Solution – Are you trying to be funny?! What it is that you are doing?
- Index creation can take a long time when the size of the index definition is greater than 16KB.
Solution – that is a single index definition that goes on for roughly 3,000 lines. You are doing things wrong.
What is the worst thing that you have seen?
Published at DZone with permission of Oren Eini, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.