Slow and excessive memory issue.

9 posts, 0 answers
  1. Rudá Cunha
    Rudá Cunha avatar
    56 posts
    Member since:
    Mar 2010

    Posted 23 Jul Link to this post

    We have a project that uses Crystal Reports for Visual Studio. And we are considering migrating to the Telerik Report.
    I downloaded the trial version 13.1.19.618
    And I created the same report we have in crystal.

    The report is large, around 18,000 records.
    But it's just data, 14 columns, no calculations, no totalizers, no graphs.

    On my development machine, this report on crystal runs in less than 2min (exports to PDF) and there is not too much memory or processing.

    Already when I will run the version of telerik. I left running more than 40min and did not finish. Memory consumption was around 2GB and processing around 30% all the time.
    I also tried to run the preview in Visual Studio, same problem.

    So I reduced it to 400 records.
    Crystal around 2 seconds to generate and display in browser.
    The telerik took about 5 minutes, with the same memory problems.

    The query runs in less than 3 seconds (18,000 records).

    I can't understand what the problem is.
    I've used the wizard, started the blank report. And always the same problem.

    I was disappointed with the performance.
  2. David
    David avatar
    124 posts
    Member since:
    Jan 2011

    Posted 23 Jul in reply to Rudá Cunha Link to this post

    The telerik reports engine is easily capable of what you trying to do.  I have written a budgeting suite for a local city.  Some of those reports are 600+ pages with up to 6 subreports per report.  Even complex items like that are no issue.  I would state the Telerik suite has a much smaller footprint than crystal. That is precisely why I abandoned Crystal.  You can actually get support from Telerik.

    Now as to your specific problems, you did not provide much actionable items  You state there are 18,000 records and 14 columns.  That sounds like a basic table report with some formatting on specific columns.  Did you check your debug window on your development box while testing?  I have noticed occasional Java errors being output here which have merit to problems.

    Are you rendering your report to a webpage or fat client?  Are you directly rendering to PDF directly?

  3. Rudá Cunha
    Rudá Cunha avatar
    56 posts
    Member since:
    Mar 2010

    Posted 24 Jul Link to this post

    I am making several comparisons.
    PDF
    XLS
    CSV

    And all types with below-expected performance.

    Yes it's very simple
    It would be like a CSV, there are only 3 columns with formatting (date and number)
    And now that I've added a Total and a header for the report to look the same. Before there was only one table with the data.

    I am using directly generating WEB in PDF or other formats (download).

    Follows the log and prints.

    001."w3wp.exe" (CLR v4.0.30319: /LM/W3SVC/1/ROOT-10-132084718677942879): Carregado "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\7e5d3187\1a429769\App_Web_jmmw4x1a.dll".
    002.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    003.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    004.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    005.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    006.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    007.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    008.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    009.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    010.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    011.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    012.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    013.Exceção gerada: 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' em Microsoft.CSharp.dll
    014."w3wp.exe" (CLR v4.0.30319: /LM/W3SVC/1/ROOT-10-132084718677942879): Carregado "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\Extensions\Microsoft\Web Tools\Browser Link\Microsoft.WebTools.BrowserLink.HtmlParser.dll".
    015."w3wp.exe" (CLR v4.0.30319: /LM/W3SVC/1/ROOT-10-132084718677942879): Carregado "C:\Windows\Microsoft.Net\assembly\GAC_MSIL\WindowsBase\v4.0_4.0.0.0__31bf3856ad364e35\WindowsBase.dll".
    016."w3wp.exe" (CLR v4.0.30319: /LM/W3SVC/1/ROOT-10-132084718677942879): Carregado "C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll".
    017.w3wp.exe Information: 0 : Unit.DotsPerInch = 96
    018.Exceção gerada: 'System.IO.FileNotFoundException' em mscorlib.dll
    019.Can not load the DocumentFormat.OpenXml assembly. The OpenXML rendering extensions will not be loaded.
    020.System.IO.FileNotFoundException: Não foi possível carregar arquivo ou assembly 'DocumentFormat.OpenXml' ou uma de suas dependências. O sistema não pode encontrar o arquivo especificado.
    021.Nome do arquivo: 'DocumentFormat.OpenXml'
    022.   em System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
    023.   em System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
    024.   em System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
    025.   em System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
    026.   em System.Reflection.Assembly.Load(String assemblyString)
    027.   em Telerik.Reporting.Processing.RenderingExtensionManager.UpdateOpenXmlExtensions(String[] extensions)
    028. 
    029.=== Informações sobre estado pré-associação ===
    030.LOG: DisplayName = DocumentFormat.OpenXml
    031. (Partial)
    032.AVI: informação de associação parcial foi fornecida para um assembly:
    033.AVI: Nome do Assembly: DocumentFormat.OpenXml | ID do Domínio: 11
    034.AVI: uma associação parcial ocorre quando somente parte do nome de exibição do assembly é fornecida.
    035.AVI: isso pode fazer com que o associador carregue um assembly incorreto.
    036.AVI: é recomendável fornecer uma identidade textual totalmente especificada para o assembly,
    037.AVI: que consiste no nome simples, na versão, na cultura e no token de chave pública.
    038.AVI: Consulte o white paper http://go.microsoft.com/fwlink/?LinkId=109270 para obter mais informações e soluções comuns para o problema.
    039.LOG: Appbase = file:///C:/GeoexPlus/GEOEX/
    040.LOG: PrivatePath inicial = C:\GeoexPlus\GEOEX\bin
    041.Chamando assembly: (Unknown).
    042.===
    043.LOG: esta associação começa no contexto de carregamento default.
    044.LOG: usando arquivo de configuração de aplicativo: C:\GeoexPlus\GEOEX\web.config
    045.LOG: usando arquivo de configuração de host: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet.config
    046.LOG: usando arquivo de configuração da máquina de C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
    047.LOG: a política não está sendo aplicada para referência neste momento (particular, personalizado, parcial ou associação de assembly baseada em local).
    048.LOG: tentando download de nova URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/root/7e5d3187/1a429769/DocumentFormat.OpenXml.DLL.
    049.LOG: tentando download de nova URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/root/7e5d3187/1a429769/DocumentFormat.OpenXml/DocumentFormat.OpenXml.DLL.
    050.LOG: tentando download de nova URL file:///C:/GeoexPlus/GEOEX/bin/DocumentFormat.OpenXml.DLL.
    051.LOG: tentando download de nova URL file:///C:/GeoexPlus/GEOEX/bin/DocumentFormat.OpenXml/DocumentFormat.OpenXml.DLL.
    052.LOG: tentando download de nova URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/root/7e5d3187/1a429769/DocumentFormat.OpenXml.EXE.
    053.LOG: tentando download de nova URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/root/7e5d3187/1a429769/DocumentFormat.OpenXml/DocumentFormat.OpenXml.EXE.
    054.LOG: tentando download de nova URL file:///C:/GeoexPlus/GEOEX/bin/DocumentFormat.OpenXml.EXE.
    055.LOG: tentando download de nova URL file:///C:/GeoexPlus/GEOEX/bin/DocumentFormat.OpenXml/DocumentFormat.OpenXml.EXE.
    056. 
    057.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.ImageRendering.PhysicalImageReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    058.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.ImageRendering.PhysicalImageReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    059.w3wp.exe Information: 0 : ExtensionInfo IMAGE successfully created.
    060.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.ImageRendering.ImageReportInteractive, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    061.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.ImageRendering.ImageReportInteractive, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    062.w3wp.exe Information: 0 : ExtensionInfo IMAGEInteractive successfully created.
    063.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.ImageRendering.PrintImageReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    064.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.ImageRendering.PrintImageReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    065.w3wp.exe Information: 0 : ExtensionInfo IMAGEPrint successfully created.
    066.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.ImageRendering.PrintPreviewImageReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    067.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.ImageRendering.PrintPreviewImageReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    068.w3wp.exe Information: 0 : ExtensionInfo IMAGEPrintPreview successfully created.
    069.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.ImageRendering.PdfReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    070.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.ImageRendering.PdfReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    071.w3wp.exe Information: 0 : ExtensionInfo PDF successfully created.
    072.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.RtfRendering.RtfReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    073.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.RtfRendering.RtfReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    074.w3wp.exe Information: 0 : ExtensionInfo RTF successfully created.
    075.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.HtmlRendering2.HtmlReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    076.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.HtmlRendering2.HtmlReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    077.w3wp.exe Information: 0 : ExtensionInfo HTML successfully created.
    078.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.HtmlRendering2.HtmlReportInteractive, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    079.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.HtmlRendering2.HtmlReportInteractive, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    080.w3wp.exe Information: 0 : ExtensionInfo HTMLInteractive successfully created.
    081.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.HtmlRendering2.MHtmlReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    082.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.HtmlRendering2.MHtmlReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    083.w3wp.exe Information: 0 : ExtensionInfo MHTML successfully created.
    084.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.Html5Rendering.Html5ReportInteractive, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    085.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.Html5Rendering.Html5ReportInteractive, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    086.w3wp.exe Information: 0 : ExtensionInfo HTML5Interactive successfully created.
    087.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.Html5Rendering.Html5Report, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    088.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.Html5Rendering.Html5Report, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    089.w3wp.exe Information: 0 : ExtensionInfo HTML5 successfully created.
    090.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.ExcelRendering.Excel97.ExcelReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    091.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.ExcelRendering.Excel97.ExcelReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    092.w3wp.exe Information: 0 : ExtensionInfo XLS successfully created.
    093.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.CsvRendering.CsvRenderingExtension, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    094.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.CsvRendering.CsvRenderingExtension, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    095.w3wp.exe Information: 0 : ExtensionInfo CSV successfully created.
    096.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.XamlRendering.SilverlightReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    097.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.XamlRendering.SilverlightReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    098.w3wp.exe Information: 0 : ExtensionInfo XAML successfully created.
    099.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.XamlRendering.SilverlightReportInteractive, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    100.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.XamlRendering.SilverlightReportInteractive, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    101.w3wp.exe Information: 0 : ExtensionInfo XAMLInteractive successfully created.
    102.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.XamlRendering.WpfReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    103.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.XamlRendering.WpfReport, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    104.w3wp.exe Information: 0 : ExtensionInfo WPFXAML successfully created.
    105.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.XamlRendering.WpfReportInteractive, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    106.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.XamlRendering.WpfReportInteractive, Telerik.Reporting, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    107.w3wp.exe Information: 0 : ExtensionInfo WPFXAMLInteractive successfully created.
    108.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.XpsRendering.XpsReport, Telerik.Reporting.XpsRendering, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    109."w3wp.exe" (CLR v4.0.30319: /LM/W3SVC/1/ROOT-10-132084718677942879): Carregado "C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Telerik.Reporting.XpsRendering\v4.0_13.1.19.618__a9d7983dfcc261be\Telerik.Reporting.XpsRendering.dll".
    110.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.XpsRendering.XpsReport, Telerik.Reporting.XpsRendering, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    111.w3wp.exe Information: 0 : ExtensionInfo XPS successfully created.
    112.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.OpenXmlRendering.Wordprocessing.WordprocessingReport, Telerik.Reporting.OpenXmlRendering, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    113."w3wp.exe" (CLR v4.0.30319: /LM/W3SVC/1/ROOT-10-132084718677942879): Carregado "C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Telerik.Reporting.OpenXmlRendering\v4.0_13.1.19.618__a9d7983dfcc261be\Telerik.Reporting.OpenXmlRendering.dll".
    114.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.OpenXmlRendering.Wordprocessing.WordprocessingReport, Telerik.Reporting.OpenXmlRendering, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    115.Exceção gerada: 'System.IO.FileNotFoundException' em Telerik.Reporting.OpenXmlRendering.dll
    116.Exceção gerada: 'System.TypeInitializationException' em Telerik.Reporting.OpenXmlRendering.dll
    117.Exceção gerada: 'System.Reflection.TargetInvocationException' em mscorlib.dll
    118.Exceção gerada: 'Telerik.Reporting.Interfaces.ExtensionManagerException' em Telerik.Reporting.dll
    119.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.OpenXmlRendering.Presentation.PresentationReport, Telerik.Reporting.OpenXmlRendering, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    120.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.OpenXmlRendering.Presentation.PresentationReport, Telerik.Reporting.OpenXmlRendering, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    121.Exceção gerada: 'System.IO.FileNotFoundException' em Telerik.Reporting.OpenXmlRendering.dll
    122.Exceção gerada: 'System.TypeInitializationException' em Telerik.Reporting.OpenXmlRendering.dll
    123.Exceção gerada: 'System.Reflection.TargetInvocationException' em mscorlib.dll
    124.Exceção gerada: 'Telerik.Reporting.Interfaces.ExtensionManagerException' em Telerik.Reporting.dll
    125.w3wp.exe Information: 0 : Creating extension info for typeName "Telerik.Reporting.OpenXmlRendering.Spreadsheet.SpreadsheetReport, Telerik.Reporting.OpenXmlRendering, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    126.w3wp.exe Information: 0 : Successfully resolved typeName "Telerik.Reporting.OpenXmlRendering.Spreadsheet.SpreadsheetReport, Telerik.Reporting.OpenXmlRendering, Version=13.1.19.618, Culture=neutral, PublicKeyToken=a9d7983dfcc261be", extensionName ""
    127.Exceção gerada: 'System.IO.FileNotFoundException' em Telerik.Reporting.OpenXmlRendering.dll
    128.Exceção gerada: 'System.TypeInitializationException' em Telerik.Reporting.OpenXmlRendering.dll
    129.Exceção gerada: 'System.Reflection.TargetInvocationException' em mscorlib.dll
    130.Exceção gerada: 'Telerik.Reporting.Interfaces.ExtensionManagerException' em Telerik.Reporting.dll
    131. 
    132.*** ReportProcessor.ProcessReport STARTED ***
    133. 
    134.*** ProcessReport #0 STARTED ***
    135.Exceção gerada: 'System.Reflection.ReflectionTypeLoadException' em mscorlib.dll
    136.Exceção gerada: 'System.Reflection.ReflectionTypeLoadException' em mscorlib.dll
    137.*** ProcessReport #0 DONE in 00:00:14.6208622 ***
    138. 
    139.*** ReportProcessor.ProcessReport DONE in 00:00:14.6546166 ***
    140. 
    141. 
    142.*** RenderReport #0 STARTED ***
    143.O thread 0x2cc4 foi fechado com o código 0 (0x0).
    144.O thread 0x1e10 foi fechado com o código 0 (0x0).
    145.O thread 0x23d4 foi fechado com o código 0 (0x0).
    146.O thread 0x2638 foi fechado com o código 0 (0x0).
    147.O thread 0x310 foi fechado com o código 0 (0x0).
    148.O thread 0x3018 foi fechado com o código 0 (0x0).
    149.*** RenderReport #0 DONE in 00:11:30.5766183 ***
    150. 
    151.O thread 0x2f08 foi fechado com o código 0 (0x0).
  4. Rudá Cunha
    Rudá Cunha avatar
    56 posts
    Member since:
    Mar 2010

    Posted 24 Jul in reply to Rudá Cunha Link to this post

    You can see that it took over 11 minutes to generate the CSV.

    *** RenderReport # 0 DONE in 00: 11: 30.5766183 ***

    And it follows the print of what the report looks like.
    Desmo leaving only the table, without the header I have the same performance.

     

    And also the bank execution that takes place in 4 seconds.

  5. David
    David avatar
    124 posts
    Member since:
    Jan 2011

    Posted 24 Jul in reply to Rudá Cunha Link to this post

    Well that was informative.  Notice all the "exceptions" being thrown?  Each takes time.  Multiple those by rows and it takes lots of time.

    The IIS version (assumption based upon the w3wp.exe references) seems to be throwing errors extensively.  Your errors suggest it is trying to remotely grab some extensions at runtime.  Those attempts are likely a source of your extensive run times.

    You have several "File not found" errors.  Those appear to be in relation to the "OpenXML" engine.  While not absolutely necessary, you get greatly improved performance with that engine versus without it.  The library is not a Telerik product but they use it if it is available on your system.  (They refer to in in the fine print on some of their buried documentation... You have to find it)  Basically visit Nuget and look for that library.  

    In short these sound like configuration issues more than report errors.  Solve the configuration issues and you should see vastly improved speeds.

    Unfortunately I am not fluent in, what I assume is Portuguese, so I cannot read all of  your error messages.  My suggestion is a careful review of those errors and try to solve them.

  6. Rudá Cunha
    Rudá Cunha avatar
    56 posts
    Member since:
    Mar 2010

    Posted 24 Jul in reply to David Link to this post

    All these errors are thrown earlier when the report file is opened.  At the time of actually loading the report.  No exceptions occur.

  7. Rudá Cunha
    Rudá Cunha avatar
    56 posts
    Member since:
    Mar 2010

    Posted 24 Jul Link to this post


    142.*** RenderReport #0 STARTED ***
    143.O thread 0x2cc4 foi fechado com o código 0 (0x0).
    144.O thread 0x1e10 foi fechado com o código 0 (0x0).
    145.O thread 0x23d4 foi fechado com o código 0 (0x0).
    146.O thread 0x2638 foi fechado com o código 0 (0x0).
    147.O thread 0x310 foi fechado com o código 0 (0x0).
    148.O thread 0x3018 foi fechado com o código 0 (0x0).
    149.*** RenderReport #0 DONE in 00:11:30.5766183 ***
  8. David
    David avatar
    124 posts
    Member since:
    Jan 2011

    Posted 25 Jul in reply to Rudá Cunha Link to this post

    I am somewhat puzzled.  Your snippets of code suggest you are rendering your reports to "screen" or "webpage".  To eliminate that, directly render it to .PDF for a test.  Here is a sample of logic I use to render reports directly to PDF skipping the display.

     

    public static FileObject BuildPdfReport(Utility u, List<WFPatrolData> srcList, DateTime dtNow)
    {
        FileObject fo = null;
     
        try
        {
            var reportProcessor = new ReportProcessor();
            if (reportProcessor != null)
            {
                var irs = new InstanceReportSource();
                if (irs != null)
                {
                    Telerik.Reporting.Report rpt = new rptWfStatusReport();
                    rpt.DataSource = srcList; // bind our report data to the report
                    irs.ReportDocument = rpt; // bind report to processing object
                    // render report using PDF to memory
                    RenderingResult result = reportProcessor.RenderReport(format: "PDF", reportSource: irs, deviceInfo: null);
                    if ((result != null) &&
                        (result.DocumentBytes.Length > 0))
                    {
                        // grab .PDF object from memory and return in our data type "FileObject"
                        string filename = string.Format(format: "WFPatrol-{0:MM-dd-yyyy}.pdf", arg0: dtNow);
                        fo = new FileObject(filename, System.Net.Mime.MediaTypeNames.Application.Pdf, result.DocumentBytes);
                    }
                    irs = null;
                }
                reportProcessor = null;
            }
        }
        catch (Exception ex)
        {
            u.HandleError("???-??????", "Internal Error", ex.Message, ex);
            fo = null;
        }
        return fo;
    }
  9. Ivan Hristov
    Admin
    Ivan Hristov avatar
    203 posts

    Posted 29 Jul Link to this post

    Hi Rudá,

    I assume the report in question is the same one that is attached in the support ticket. I already answered it with some general suggestions about PDF rendering, but here I noticed that the used rendering extension is CSV, which is not really suitable for exporting information from Table-based items. As mentioned in Design Considerations For CSV Rendering, the CSV rendering traverses the table structure, trying to "flatten" the hierarchy and this process requires a significant processing time. In this case I strongly suggest to avoid using Table and put the text boxes into the report's Detail Section. Using this approach, the CSV export takes ~6 seconds on my machine to export 18000 rows of dummy data with the Consulta report definition. As a rule of thumb, the best performance is obtained by using the simplest layout, so a flat record list is best represented using the report's Detail Section.

    @David, we're really glad that Telerik Reporting meets your expectations and thank you for taking the time to examine the current problem. I just wanted to clarify that the report extensions are evaluated prior to rendering the report, and if OpenXML rendering extension is missing, this will not affect the rendering performance itself. You are right, each thrown exception is "expensive", but in this case it will be thrown just once and, as a result, the OpenXML exporting formats will not be available. I also agree that, as you mentioned, it is always recommended to render large reports directly using the ReportProcessor, rather than showing them in the report viewer first and then export to the desired format.

    I hope my explanations make sense. In case you need further assistance, please do not hesitate to ask.

    Regards,
    Ivan Hristov
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top