|
|
Originally Posted by: Paul Rayman  Hello,
I apologize for the delay in responding. Currently, a stable working solution has not yet been found. :(
|
|
|
Hello,
I apologize for the delay in responding. Currently, a stable working solution has not yet been found.
|
|
|
Hi Paul, Originally Posted by: Paul Rayman  I apologize for the delay in responding. This problem requires additional research on the capabilities of the Pdfium engine. Any hope for a solution? We are heading towards release, and this issue is slowly becoming a blocker.
|
|
|
Hi Paul, Originally Posted by: Paul Rayman  I apologize for the delay in responding. This problem requires additional research on the capabilities of the Pdfium engine. Any success on the topic? This issue is biting us quite badly at the moment. We already thought about using pdfium to read PDFs, and then old library to write. But, it seems, that even on "normal" read some documents can have 20 seconds long .Dispose() calls, which makes parallelism the only possible solution.
|
|
|
I apologize for the delay in responding. This problem requires additional research on the capabilities of the Pdfium engine.
|
|
|
Hi
Paul Rayman
, Any news on the subject? Did you manage to reproduce those problems?
|
|
|
Originally Posted by: Paul Rayman  Are you using latest version of SDK? By the way, the same approx. 10x slowdown occurs when processing pages of one document in parallel.
|
|
|
Originally Posted by: Paul Rayman  Are you using latest version of SDK? Hi Paul, The problem is still reproducible with the latest SDK. I have made a short repro project, see PdfiumNetParallelism.zip (697kb) downloaded 43 time(s).. Just drop Patagames.Pdf.dll and pdfium.dll from the SDK to the ParallelPdfTest folder - the project is referencing those (had to remove them, as zip was too big for this forum). The code is simple, you do not need explanations. Just run it, and you will see that in multithreaded scenario SDK is about 10 times slower.
|
|
|
Originally Posted by: Paul Rayman  Are you using latest version of SDK? Strange... We saw the problem on one computer (DELL Intel machine), but we could not reproduce it in our testing environment (not the same kind of machine). The problem is, that the guy on the problem-machine is on vacation now, and will be back on August 12th. :( So, we will not be able to confirm if updating SDK fixed the problem until then. Have a nice summer!
|
|
|
Originally Posted by: Paul Rayman  Are you using latest version of SDK? No, we had 4.7.2704. I updated it now to the latest 4.11.2704, and will ask a tester to check if the problem is still there. Was something related to threading fixed recently?
|