Skip to content

Performance

Paul Stovell edited this page Apr 20, 2020 · 24 revisions

This page has tips for getting better performance out of Nevermore.

Nevermore 12.0+ is generally faster for most queries, and with larger documents, uses much less memory. If you're on an older version, consider upgrading. See what's new in Nevermore 12.0+ for benchmarks.

If the time spent reading and writing JSON from the database and transferring it over the network between the application and SQL Server is a concern, consider enabling compression. This makes a very big difference in bandwidth-constrained environments, especially for larger documents.

Nevermore uses JSON.NET by default. You could instead use the System.Text.Json serializer, which seems to use less memory. You can do this by setting your own IDocumentSerializer on the store configuration. However, System.Text.Json makes the assumption that everything you do is in UTF-8, which isn't the case in SQL Server, so you might waste time converting anyway.

Also add:

How nevermore compares to hand-rolling SQL

What Nevermore is optimized for

How Nevermore works

Clone this wiki locally