This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
While profiling my page, I load 5000 records into a collection and set it in the request as an attribute. It took about 20 minutes to show the page when run the web app in Netbeans. I found out that MonitorFilter calles getString() on the collection, which in turn calls getString of each record. Each records has a toString which returns some descriptions. So, this collection's getString really cost time and memory to do this. I am not sure why MonitorFilter do this, but I think it needs a way around this, because this just does not work.
I think that profiling should turn off HTTP monitor. OTOH you can turn it off manually in Tomcat's properties (Runtime window).
Thank you for the comment. I didn't know I can turn it off. Please also note that I didn't run this under profiling. When I see this performance problem, then I profile the app, and strangely (actually, a good thing, but little odd), this MonitorFilter does not show up at all in the profile. In another word, it's good not to profile Netbeans specific stuff, but unfortunately, in this particular case, without that, I cannot know MonitorFilter causes this (I use all default stuff, maybe learning this abit would help).
We do not plan to fix this, since it is not a very common usecase. Besides, the monitor can always be turned off, when working with large requests.