![]() We have attempted to tweak each of the ImageMagick resource limit options. Without this we saw our primary drive consistently getting filled up / drained along with image preview generation. We ended up creating a separate dedicated mounted drive for ImageMagick/Ghostscript file management - 60GB in size. While this has now somewhat subsided - we are still seeing large files having a substantial impact to our system. We also have OpenOffice installed and enabled to facilitate document conversions.Īfter our initial upgrade release last week we had several server crashes which we now believe to be a result of the system being overloaded by attempting to play "catch up" on the document image preview backlog as clients began to navigate around the upgraded system - triggering all of these previews. I should also mention that we migrated our Document Library over to the S3Store implementation as part of our upgrade release. ![]() We have allocated 4GB of RAM to our LR instance. This has 2 CPUs, 7.5GB of RAM and 8GB of disk space. ![]() ![]() We are running on an m1.large EC2 Amazon Linux AMI instance. While we have attempted to utilize the ImageMagick resource limit constraint properties (very useful to have BTW - thx!) available in the Control Panel - it appears that ImageMagick itself is not the problem. Since upgrading to 6.1.20 EE GA2 and enabling the document library preview functionality we have noticed a severe impact to the performance of our production instance. Some of our client's documents that get uploaded can run into the several thousand pages length. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |