Which jcdcdev.Umbraco.ReadingTime version are you using?
16.0.x
Which Umbraco version are you using? For example: 10.4.0 - don't just write v10
16.5.0
Bug summary
Hi James,
Great work on the package, we have noticed when using we are seeing high database usage, as the client has a large blog/news section and each page or related content like latest news hits the database.
I have a solution but it is a fairly large change to the approach.
Move from away from the publishing event instead use the saving event, This allows for storing within the property the raw seconds.
Additionally (I haven't attempted this one yet) We can also check to see if what properties if any are Dirty and only recalculate if one of them is a supported datatype. Reducing the need to recalculate on every save.
I have a working solution, that I need to port over on my machine to the v17 branch so I can create a PR.
Thanks
Matt
Steps to reproduce
use the package as normal.
Expected result / actual result
No response
Which jcdcdev.Umbraco.ReadingTime version are you using?
16.0.x
Which Umbraco version are you using? For example: 10.4.0 - don't just write v10
16.5.0
Bug summary
Hi James,
Great work on the package, we have noticed when using we are seeing high database usage, as the client has a large blog/news section and each page or related content like latest news hits the database.
I have a solution but it is a fairly large change to the approach.
Move from away from the publishing event instead use the saving event, This allows for storing within the property the raw seconds.
Additionally (I haven't attempted this one yet) We can also check to see if what properties if any are Dirty and only recalculate if one of them is a supported datatype. Reducing the need to recalculate on every save.
I have a working solution, that I need to port over on my machine to the v17 branch so I can create a PR.
Thanks
Matt
Steps to reproduce
use the package as normal.
Expected result / actual result
No response