Slow .MSG to .PDF Conversion in .NET

Hi,

We have updated Groupdocs.Conversion to version 23.6.0 (previous version was 22.9.0) and we now see that the conversion (.msg to .pdf) takes much longer (14 to 15 seconds) than with the previous version (4 to 5 seconds).

Below is the code we are using.

// Set GroupDocs.Conversion license
new License().SetLicense("GroupDocs.Conversion.NET.lic");

// Define file paths for input .msg and output .pdf
var pathMsg = Path.Combine(Environment.CurrentDirectory, $"Data\\TESTWV.msg");
var pathPdf = Path.Combine(Environment.CurrentDirectory, $"Data\\TESTWV.pdf");

// Get possible conversions for .msg files
var possibleConversions = Converter.GetPossibleConversions(".msg");

// Disable conversion of owned emails to optimize performance
((EmailLoadOptions)possibleConversions.LoadOptions).ConvertOwned = false;

// Create a new FileStream for the output .pdf file
using (var fsPdf = new FileStream(pathPdf, FileMode.CreateNew, FileAccess.ReadWrite, FileShare.ReadWrite))
{
    // Open .msg file as a document stream
    using (var documentStream = File.OpenRead(pathMsg))
    {
        // Initialize the converter with the document stream and load options
        using (var converter = new Converter(() => documentStream, () => possibleConversions.LoadOptions))
        {
            // Set options for PDF conversion
            var options = new PdfConvertOptions();

            // Perform the conversion and save the result in the FileStream
            converter.Convert(() => fsPdf, options);
        }
    }
}

Are we doing something wrong or what could be the reason for this performance issue?

Any help in this is welcome,
Regards Wiel

1 Like

Hello @WielV,

Would it be possible for you to provide the following information:

  • The source file.
  • Is your license valid for the new version?
  • Details about your development environment (e.g., OS version, .NET version)?

Thank you!

TestGroupDocsConversion.zip (31.4 KB)
Result Version-22.9.0.png (4.0 KB)
Result Version-23.6.0.png (4.0 KB)
Hi Atir,

I’ve attached a zip file with the source code (cleared the .lic file) and 2 screenshots with test results.

How do I now if our license is valid for the new version? The subscription expiry is ‘20240717’.

Environment details: .NET version is ‘net7.0’ and os is Windows 10 Pro (Version: 22H2 - OS Build: 19045.3208).

If you need more info, then please let me know.

Regards Wiel

@WielV

Are you getting evaluation watermark in the output file? You can also share the license file in the private message.

No, there is no evaluation watermark in the output file (see attached pdf files).TESTWV - V22.9.0.pdf (106.3 KB)
TESTWV - V23.6.0.pdf (104.1 KB)

@WielV
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CONVERSIONNET-6202

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

Hi Atir,

Another difference between these versions, version 22.9.0 converts images in an email and version 23.6.0 does not (see pdf attachments in previous message)!

Regards, Wiel

@WielV

Indeed, we are already investigating this discrepancy.

@WielV

We’re pleased to inform you that the improvement you mentioned will be included in the upcoming release, version 23.7. The expected conversion time is projected to be around 4 seconds once again. Once the release is on-board, we’ll notify you.

The issues you have found earlier (filed as CONVERSIONNET-6202) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov

Hi,

I did some tests with the new version 23.7.0, but I don’t see any improvements, 23.7.0 isn’t really that much faster than 23.6.0! The conversion from .msg to .pdf is still slow and the image conversion problem is also not fixed.

Another big difference we see between version 22.9.0 and versions 23.6.0 and 23.7.0 is that with version 22.9.0 the ‘SetLicense(…)’ takes quite a long time and almost no time for the other versions (but the conversion of these versions is much slower).

Regards,
WielV

1 Like

@WielV

We are really sorry for the inconvenience caused. We have logged these issues for further investigation. Your investigation ticket ID is CONVERSIONNET-6233. We’ll notify you in case of any update.

Hi,

Any news on this issue?

Regards,
WielV

@WielV

This ticket is still under investigation.

Hi,

Is there still no news on this issue?

Regards,
WielV

@WielV

The ticket is still under progress.

The issues you have found earlier (filed as CONVERSIONNET-6233) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov