@Mohit_Tandel
Could you please share a sample .eml file that reproduces the issue, if possible? This would help us inspect the file metadata, encoding, embedded content, attachments, headers, and any other values that may affect rendering time.
The large difference between the local environment and production environment is important here. If the same small .eml file opens in a few seconds locally but takes several minutes in production, this may indicate an environment-specific issue.
Your current EmailConfig and DocOptions look acceptable for testing:
For the next test, we recommend temporarily disabling the watermark to isolate the rendering performance:
var documentOptions = new DocOptions
{
ImageResolution = 110,
TimeOut = 600,
Watermark = "" //
};
Also, please use the same JavaScript viewer configuration recommended for large or potentially slow documents:
objctlDoc = $("#div_viewer").docViewer(
{
debugMode: false,
// The viewer does not add all pages and thumbnails to the DOM at once.
// It loads them in blocks, which is safer for large or slow-rendering documents.
largeDoc: true,
// cacheEnabled=true:
// - smoother navigation for small/medium documents
// - more anticipated requests to DocImage.axd
// - more server load
// - more browser memory usage
//
// cacheEnabled=false:
// - loads only what the user is actually viewing
// - less pressure on the server
// - better when diagnosing performance issues
cacheEnabled: false,
// autoLoad=true:
// - preloads/renders the whole document
// - useful if you want everything ready for navigation/printing
// - can be expensive if the document or environment is slow
//
// autoLoad=false:
// - loads on demand
// - recommended while diagnosing performance issues
autoLoad: false
});
Please share the sample .eml file and, if possible, the opening-time logs from both environments using the same file and configuration. That will help us compare whether the delay is happening during file access, email parsing, rendering, or image/page generation.