Codejock Developer Community : Report::ResetContent() performance..... http://forum.codejock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Sun, 19 Apr 2026 04:15:14 +0000 Wed, 09 Feb 2011 05:30:16 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 forum.codejock.com/RSS_post_feed.asp?TID=10285 <![CDATA[Codejock Developer Community]]> http://forum.codejock.com/forum_images/codejock-logo.gif http://forum.codejock.com/ <![CDATA[Report::ResetContent() performance..... : This weekend I investigated this...]]> http://forum.codejock.com/forum_posts.asp?TID=10285&PID=62471&title=reportresetcontent-performance#62471 Author: Marco1
Subject: 10285
Posted: 09 February 2011 at 5:30am

This weekend I investigated this case a little deeper.
Long story short, it seems that string classes (esp. CString) are very slow in destruction (due to discrete delete).
If 50000 CStrings need to be destructed, (mem management) requires significant time.

A list full of ReportRecordItemNumbers only is fairly fast.

In the moment I'm testing STL containers and own ReportRecordItems which contains only pointers to the STL stored strings to avoid CStings. Don't know yet, if that is sooo much better.

Any suggestions are really appreciated.
]]> Wed, 09 Feb 2011 05:30:16 +0000 http://forum.codejock.com/forum_posts.asp?TID=10285&PID=62471&title=reportresetcontent-performance#62471 <![CDATA[Report::ResetContent() performance..... : Has anyone found a solution for...]]> http://forum.codejock.com/forum_posts.asp?TID=10285&PID=62404&title=reportresetcontent-performance#62404 Author: Marco1
Subject: 10285
Posted: 02 February 2011 at 2:38pm

Has anyone found a solution for this?
I tested ResetContent (which is called during report destruction) with PerformanceTestDlg in the CJ Report sample. When I set the row count in the example to 10000 (instead of 1000) it takes about 15 seconds(!) on my notebook just for ResetContent - compiled as RELEASE version.
I know that delete is a very expensive function, but 15s for 10k rows are not acceptable.
Using virtual mode is not a good option due to sorting/grouping restrictions.


... and I already have the slight feeling that my customer won't accept that Confused
]]> Wed, 02 Feb 2011 14:38:37 +0000 http://forum.codejock.com/forum_posts.asp?TID=10285&PID=62404&title=reportresetcontent-performance#62404 <![CDATA[Report::ResetContent() performance..... : If you&#039;re testing with...]]> http://forum.codejock.com/forum_posts.asp?TID=10285&PID=33976&title=reportresetcontent-performance#33976 Author: Smucker
Subject: 10285
Posted: 20 April 2008 at 4:17am

If you're testing with a compiled debug version, the C/C++ runtime libraries take a lot longer to release memory, especially for 100K items (assuming these are allocated individually). The debug code scans each block (paging it in if necessary) to check for heap corruption, etc.

For further speed, if you create your own heap HeapCreate(), and use HeapAlloc() to allocate only the report items, you can clear them all very quickly, by simply deleting and recreating the heap. This has a nice side effect of  returning the memory to the system immediately, though some leak detectors may not recognize this and report all the items as leaked.

Also, if your items are always allocated by a single thread, you can create the heap using HEAP_NO_SERIALIZE flag,  reducing locking overhead and speeding allocations.

]]> Sun, 20 Apr 2008 04:17:21 +0000 http://forum.codejock.com/forum_posts.asp?TID=10285&PID=33976&title=reportresetcontent-performance#33976 <![CDATA[Report::ResetContent() performance..... : I have several reports that might...]]> http://forum.codejock.com/forum_posts.asp?TID=10285&PID=33864&title=reportresetcontent-performance#33864 Author: ddlittle
Subject: 10285
Posted: 17 April 2008 at 3:57pm

I have several reports that might have 100K lines in them (not at the same level, say 1000 lines, each with 100 children).  Populating the lines is very fast, but if my user opens another model, I do a ResetContent() prior to re-populating and that can sometimes take 500 seconds or so - which is beyond most user's patience, they think the machine is dead...
 
I tried the example program "ReportCustomHeap" and noticed similar performance issues.  When adding records, it's possible to pre-allocate memory, but removing them is apparently a one-at-a-time operation. 
 
Anybody have any ideas?
 
 
]]> Thu, 17 Apr 2008 15:57:40 +0000 http://forum.codejock.com/forum_posts.asp?TID=10285&PID=33864&title=reportresetcontent-performance#33864