One benefit of Struts MVC is that you can unit test, or performance test each layer.
Struts is not slow, but you model access could be slow. Struts is Model (and View) agnostic.
So you should stress test (unit test) the performance of your model design isolated, before Struts even sees it.


Likely that your model design need improvement. For example, even when using native DB drivers (DLL level without JDBC) one can't see any rows until ALL the rows are transmited (rows are not streamed). So becuase of native drivers, JDBC does not see row 1 unill your row 17,000 is sent by the DB. Sometimes people write EIS and DSS systems becuse of this,that does dimensional subsets of data and you drill down, and then have a seperate application to batch printing.

I guess consider rediesng to EIS/DSS, or use a native reporting engine for that many rows (with good memory managment).

Struts has no reporting, but.... many people use http://ireport.sourceforge.net and jAaper, without the full MVC as a Struts module, but that would be for well designed systems.

hth,
.V

Prasad, Kamakshya wrote:
Hi All,
I believe Struts uses reflection api for populating the jsp from form
bean. Therefore, if jsp is generating a csv containing a big table with
lots of rows (like generating reports), then form bean properties has to
be called in a loop (using logic-iterate). Will this be a performance
issue (using reflection api and also jsp tags)? As in the system user can choose to view the report either in an html or
download it in csv, we are using the single jsp to do both, only the
content type is changed based on the selection.
Sometimes, the report data can go upto 17,000 rows
Please advise me on the same and correct me if I am wrong anywhere.
KP




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to