I would like to support this - local resources for transformation of PDFs is WAY underused. Multithreaded and more RAM usage is paramount.
4000 Pages is nothing - especially if it's from MS word and it's just plaintext. That should take a few minutes, tops, on a robust machine.
I have a 256GB + dual socket CPU (Xeon HP server hardware) that I'm using for Adobe, only. It's shameful how little resources Adobe can use, and I suspect it's for pushing us to "upload to their cloud" so they can use AI on it or something. This won't work for me, as I have very sensitive patent controlled documents that I will never upload, but I need to OCR and file size reduce. This is where my older servers come in handy. But it's REALLY slow going, and as the OP mentioned, it will crash / not respond at random times.
Adobe really could recapture a lot of goodwill by recompiling Acrobat DC/Pro to be fully 64bit, fully multithreaded, and fully capable of using maximum resources should we want it to.
RyanM206
supported this idea
·
I would like to support this - local resources for transformation of PDFs is WAY underused. Multithreaded and more RAM usage is paramount.
4000 Pages is nothing - especially if it's from MS word and it's just plaintext. That should take a few minutes, tops, on a robust machine.
I have a 256GB + dual socket CPU (Xeon HP server hardware) that I'm using for Adobe, only. It's shameful how little resources Adobe can use, and I suspect it's for pushing us to "upload to their cloud" so they can use AI on it or something. This won't work for me, as I have very sensitive patent controlled documents that I will never upload, but I need to OCR and file size reduce. This is where my older servers come in handy. But it's REALLY slow going, and as the OP mentioned, it will crash / not respond at random times.
Adobe really could recapture a lot of goodwill by recompiling Acrobat DC/Pro to be fully 64bit, fully multithreaded, and fully capable of using maximum resources should we want it to.