The popular NotFound handler for ASP.NET Core and Optimizely, enabling better control over your 404 page in addition to allowing redirects for old URLs that no longer works.
We identified a performance degradation in this query when the table has over 2 million records:
(@contentKey nvarchar(2000))SELECT TOP 1 Id, ContentKey, Urls, CreatedUtc
FROM [dbo].[NotFoundHandler.ContentUrlHistory]
WHERE ContentKey = @contentKey
ORDER BY CreatedUtc DESC
To address this, we are adding an index on ContentKey using a new column that will store a hash of the ContentKey.
I ran some benchmarks, and as a result, we expect to improve performance by 10x with this approach when the table becomes large.
We identified a performance degradation in this query when the table has over 2 million records:
To address this, we are adding an index on ContentKey using a new column that will store a hash of the ContentKey.
I ran some benchmarks, and as a result, we expect to improve performance by 10x with this approach when the table becomes large.
https://github.com/Geta/geta-notfoundhandler/issues/129