Databasereader Not enough storage not solved

[maxmind]

Databasereader Not enough storage not solved

[oschwald]

There are many different options to cache the reader object between web requests. Setting up the reader object is expensive and it should not be done each request.

As for opening the reader many, many times as you appear to be doing, you likely would not have the problem when using the memory mode. The error you allude to appears to be a limitation of how memory mapped files are implemented in Windows.

[corradin]

I could look into caching thanks for that :). Changing the memory mode will cause memory to go sky high, since after each request memory is increased. I assume the Maxmind DB is loaded into the LOH (Large Object Heap) and .NET has some vulnerabilities in cleaning up the LOH.

[oschwald]

Yeah, at the very least, using memory mode would cause some serious pressure on the garbage collector. Using one of the caching options is the best solution.

[manigandham]

@SP0NG

HTTP is stateless so any web app servicing these requests will need to maintain it's own state, but that being said there's no reason why you can't share services across requests. This geolocation database is just as stateless as your app.

Most services and modules used by asp.net are also implemented as single instances that live for the life of the appdomain so this is an extremely common pattern. You can just use a global static variable holding the database reader that's initialized in the application startup (and disposed in the app shutdown).

[oschwald]

Closing as using a new reader for every request is not recommended. This particular error appears to be an artifact of memory mapping on Windows. If you must create a new reader for every request, it is recommended that you don't use the memory mapping mode.