Umbraco 8.12 huge memory usage (5.5GB) and very slow backend
We have just put a site live today using a IIS and SQL setup i.e. not on the cloud. We had some issues during development around sql timeout but these were resolved by moving to seperate SQL server. We have pushed live and the site is eating 5.5GB. Any suggestions on how to fix. The site is very slow in the backend to the point it takes a minute to load the content tree.
Publish status reports
Database cache is ok. ContentStore contains 4634 items and has 2 generations and 1 snapshot. MediaStore contains 696 items and has 1 generation and 1 snapshot.
Any suggestions, we have sites with a lot more nodes than this in 8.5 and less with no problems.
It seems we have resolved to an extent. The main problem seemed to be ImageProcessor attempting to process images that were referenced but didn't actually exist as a file. Once we moved files over the memory usage came down to 500-600mb. Suggests there might be something up with ImageProcessor when it is trying to process an image that doesn't actually exist?
Umbraco 8.12 huge memory usage (5.5GB) and very slow backend
We have just put a site live today using a IIS and SQL setup i.e. not on the cloud. We had some issues during development around sql timeout but these were resolved by moving to seperate SQL server. We have pushed live and the site is eating 5.5GB. Any suggestions on how to fix. The site is very slow in the backend to the point it takes a minute to load the content tree.
Publish status reports Database cache is ok. ContentStore contains 4634 items and has 2 generations and 1 snapshot. MediaStore contains 696 items and has 1 generation and 1 snapshot.
Any suggestions, we have sites with a lot more nodes than this in 8.5 and less with no problems.
Hi Tim
Are you using Examine indexes? Check that indexes are working fine.
Thanks,
Alex
Hi Alex,
It seems we have resolved to an extent. The main problem seemed to be ImageProcessor attempting to process images that were referenced but didn't actually exist as a file. Once we moved files over the memory usage came down to 500-600mb. Suggests there might be something up with ImageProcessor when it is trying to process an image that doesn't actually exist?
Thanks
Tim
Actually, it's strange that you are trying to show images that don't exist. Can you check images before rendering?
Thanks,
Alex
is working on a reply...