Our reports are all dynamically linked to the database with the DataSourceConnections.SetConnection() method. Now, some customers are complaining about this behavior.įor you information, we are using the ReportDocument.Load() method to load documents. Prior to this, we were using Delphi with the Crystal Report 10 runtime. Each time I ran the tests, it is the assembly that is the slowest (and by far) among them all. I've discovered that, while most of the CR assemblies takes less than 500 milliseconds to load, there is one that takes at least 3 seconds (20 seconds sometimes) to load : 圜odeDecoder. Using the event, I've tracked the assemblies being loaded when opening the report and the start time of the loading.
While reading the threads, I realized that the first load implies some assembly loading from the Framework (which is normal).īut since i can take as long as 20-30 seconds to load the first report, I ran some test.
If I open a report, close it and open it a second time, the second time is much faster than the first. When we try to open a report in an application, the first report loading is unusally slower than the others. Since the runtime is in x86 only, the engine is compiled in x86 (not ANY CPU) For the CR runtime, we tested on machines with the SP2 and SP3 versions, as well as on a computer with Crystal Report Developper installed (v12.3.0.601) with no runtimes. The code is in C#, targeted on the Framework 3.5 SP1.
We based the engine on the Crystal Report 2008 version (). This engine will be used in our applications to show, print and export reports. We are currently developping a new report engine based on the. Since I've found nothing in particular, I started this one. I search this forum to find another thread regarding this issue.
0 kommentar(er)
