| |
Data Dynamics Reports Support
Started by Wind Pan at 07-21-2010 7:31 PM. Topic has 25 replies.
  
|
|
Sort Posts:
|
|
|
|
 07-21-2010, 7:31 PM
|
Wind Pan
Joined on 03-24-2010
Posts 46
|
|
|
Please also send me the link which contains the fix for memory leak. I will see if my issue is solved with this fix.
thanks,
Wind
|
|
|
|
|
Report
|
|
|
|
|
07-22-2010, 1:46 AM
|
Sergey
Joined on 08-28-2004
Novosibirsk, Russia
Posts 3,015
|
|
|
|
Hello,
I've sent you the download link via email.
Sergey Abakumoff
GrapeCity
|
|
|
|
|
Report
|
|
|
|
|
07-23-2010, 4:01 AM
|
blett
Joined on 01-15-2009
Posts 20
|
Re: Possible Memory Leak
Attachment: 2.JPG
|
|
|
|
|
|
Hi Sergey,
I ran a report which should have more than 20,000 pages with DDR 1.6.1871.41. It crashed after one and half hours with 9621 pages rendered. Here is the picture I captured. Thanks!
 
|
|
|
|
|
Report
|
|
|
|
|
07-23-2010, 11:18 AM
|
Scott
Joined on 08-28-2004
Columbus, Ohio
Posts 546
|
|
|
|
It is quite possible that such a large report - 20,000 pages - is simply going to require more memory than your machine has. Just to consider a purely hypothetical example, if each page had a 500KB image on it, a 20,000 page report could consume 10GB of memory. Now, obviously this is just a contrived example and in your situation there may be a genuine problem. If you suspect a problem please reply with more information. Ideally the report attached and some sample data will enable us to investigate most effectively.
|
|
|
|
|
Report
|
|
|
|
|
07-23-2010, 12:00 PM
|
DanReber
Joined on 09-05-2003
Wyomissing, PA
Posts 363
|
|
|
|
blett,
Add GDI objects to the Task Manger and see if the app fails at 10K. 10K is the limit that the OS can handle. At least it used to be...
Dan Reber
|
|
|
|
|
Report
|
|
|
|
|
07-23-2010, 1:35 PM
|
Justin
Joined on 09-17-2003
Posts 122
|
|
|
|
"It is quite possible that such a large report - 20,000 pages - is simply going to require more memory than your machine has."
I would say this is most likely the case.
Again in my sample I only had 70,000 records with a single column which ended up being 1892 pages.
This dataset is only 5 MB serialized as bloated XML, yet in the report runtime ends up using 300-500 MB of ram when rendered to a simple table with no borders even!
So I think bottom line, DD Reports is currently not a good reporting package when dealing with large datasets, that generate many pages of output because of it excessive ram usage in that scenario.
I believe there is probably quite a bit of room for memory optimization in there though, I know we came from using Active Reports ActiveX version and it could easily generate 1800 pages of more complex output with much lower memory usage.
I think if I where to group the large dataset and say do a graph with it, it uses very little ram, so it seems to be the number of controls rendered not the number of rows in the dataset that matters very much.
This is ok for what we are using it for so far, but if you need many rows of output you should be aware of its memory usage especially in a shared resource scenario like the web viewer in a web site with potentially many concurrent users.
|
|
|
|
|
Report
|
|
|
|
|
07-27-2010, 12:53 PM
|
James Johnson - DD
Joined on 01-05-2006
Columbus, Ohio
Posts 502
|
|
|
|
I just want to let everyone know what is going on. Right now we are looking into the memory consumption of the web viewer, we will be gathering some data on what is making up the bulk of the memory usage so we can decide how to best approach this issue.
James
|
|
|
|
|
Report
|
|
|
|
|
07-27-2010, 1:08 PM
|
Justin
Joined on 09-17-2003
Posts 122
|
|
|
|
Just to clarify in my testing ram usage is similar in both the web and winform viewer, so it seems related to the core engine not which viewer is being used.
It is just exacerbated in the webviewer because more than one could be generated concurrently by different users, vs the winform which is usually just a single report at a time on a workstation.
Also targeting x86 vs any cpu seems to make a noticeable reduction in memory usage, I would guess because you are creating a whole lot of instances of something and the pointers are 64bits instead of 32bits on any cpu on a 64bit machine.
|
|
|
|
|
Report
|
|
|
|
|
07-30-2010, 5:33 AM
|
Amit Pal
Joined on 12-11-2008
Posts 855
|
|
|
|
Hello,
Case 147883 (Refreshing WebReportViewer can causes memory leak) and Case 147874 (Rendering multiple reports in Viewer causes memory leak) has been fixed in the latest build (1.6.1871.45) of DataDynamics Reports.
You may download this build from here:
ftp://ftp.fpoint.com/ActiveReports/builds/1.6.1871.45.zip
Amit Pal
GrapeCity- DataDynamics
|
|
|
|
|
Report
|
|
|
|
|
08-04-2010, 5:24 PM
|
Wind Pan
Joined on 03-24-2010
Posts 46
|
|
|
|
Reproduced out of memory with the latest build (1.6.1871.45) today with a large amount of data. BTW, is DDR putting all of the data queried from DB to the memory? Is it possible only to put some and re-run the query according to selection?
|
|
|
|
|
Report
|
|
|
|
|
08-06-2010, 6:16 AM
|
Amit Pal
Joined on 12-11-2008
Posts 855
|
|
|
|
Just to keep everything related to one thread in the same thread, I have replied to your post here:
http://www.datadynamics.com/forums/134675/ShowPost.aspx
Amit Pal
GrapeCity- DataDynamics
|
|
|
|
|
Report
|
|
|
|
|
|
Page 2 of 2 (26 items)
|
< 1 2 |
|
|
|
GrapeCity » Product Support » Data Dynamics R... » Possible Memory Leak
|
|
|
|
|