I think this rings true Tim. You commented on our recent-ish CacheDependency memory leak bug which was validated relatively quickly, but it took a lot of pushing and a long wait to get released into 7.15.5.
We upgraded and immediately noticed a huge CPU issue when we were being crawled. 7.14 handled that traffic without issue, but clearly 7.15.5 hadn't been load tested. The whole process of upgrading, testing, then downgrading has cost us so much time I haven't been able to get anyone on this to investigate further, but it does seem someone else has noted the same issue: our.umbraco.com/forum/using-umbrac...
Clearly while fixing bugs the team have introduced a new, and major, issue. We were seeing our CPU rapidly ramp up to 100% during the crawl, but then NOT RECOVER for hours after the traffic had subsided. Somehow the site stayed operational but that was something of a miracle.
I'll try and get this raised, but again I don't have high hopes for a fix (that actually works), and our client is not ready to upgrade to v8 yet so we're caught between a memory leak and CPU overload!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think this rings true Tim. You commented on our recent-ish CacheDependency memory leak bug which was validated relatively quickly, but it took a lot of pushing and a long wait to get released into 7.15.5.
We upgraded and immediately noticed a huge CPU issue when we were being crawled. 7.14 handled that traffic without issue, but clearly 7.15.5 hadn't been load tested. The whole process of upgrading, testing, then downgrading has cost us so much time I haven't been able to get anyone on this to investigate further, but it does seem someone else has noted the same issue:
our.umbraco.com/forum/using-umbrac...
Clearly while fixing bugs the team have introduced a new, and major, issue. We were seeing our CPU rapidly ramp up to 100% during the crawl, but then NOT RECOVER for hours after the traffic had subsided. Somehow the site stayed operational but that was something of a miracle.
I'll try and get this raised, but again I don't have high hopes for a fix (that actually works), and our client is not ready to upgrade to v8 yet so we're caught between a memory leak and CPU overload!