kipusoep/UrlTracker

Newest NuGet DLL results in poor performance/bug with images

Ambertvu opened this issue · 6 comments

followed the conversation of the last few days by @daniel-chenery and @kipusoep .

Sadly when using this new DLL in our project, it (bugs?) and increases CPU usage by alot on first load.

We've tested this in a relativly simple website with about 200 redirects.

When adding the DLL letting it build and doing a first load, it would take high CPU usage on our server (up to 50%) for the entire duration it was loading (about 30 seconds), normally this website loads in under 3 seconds. Especially the images would load very very slowly.

After the first load it would work relatively normal. But when doing a hard refresh everything would spike again (again it may be an issue with the DLL and the images that are loaded?)

When restoring the original DLL everything would work fine again, sadly the YSOD issue is now back.

We've tested this in local enviroment and in an online enviroment, same issue.

Edit: Tested this in 2 other products, same issue.

The only significant change is the switch to the DatabaseContext from SQLHelper, which would explain the slowness on first load (it's pulling from the database). However, a database call has always been there.
Perhaps this one does it slightly differently.

I'm really not sure why your images would be affected though.

UrlTracker will run on every single request for the force redirect rules. @Rann1 how many force redirect rules are there?

@kipusoep about 40-50 I think. My colleague set it to Force Redirect (as that fixed the YSOD / Metadata read error aswell) only for the pages that would 404 faulty.

Allthough the other 2 projects hardly have any force redirects I think, if you want I could check

@Rann1 Would you mind giving the latest BETA (13.14) a spin, and see if this has improved performance for you? :)

Closing this due to inactivity. Feel free to come back and comment with more information though :)

Just updated this on a live enviroment which had issues with this plugin before. Seems all runs fine now with the 3.14.1 update! No issues so far.