>From the orignal bugpost:

------------snip--------
 Average Size of a 
Workbook is 30 Col X 1000 Rows X 25 Worksheets (file size is approx 5-6 MB).

 
...stress testing with 30 Concurrent user ....HSSFSheet objects are taking
almost 100 MB space.
------------snip--------

File size is 5-6MB & 30 concurrent users => 30*5=150MB 
-- so there's one reason why HSSFSheet objects are taking ~100MB?

Anyway, if you have such a concurrency requirement, 
there are multiple ways you can tackle the issue at 
the architecture level, one of which is as follows:
1. Have a sheet-generating 'server' (servlet, daemon
process etc) that queues requests and process at most
N at a time in a multithreaded fashion where N is the
number of sheets that can be handled with enough 
memory to spare.
  If you are using J2EE, this could be implemented using
MDB or just JMS. If its a Web Applciation you could have 
a servlet and set the max-threads in thread pool for this 
servlet to N.

HTH,
~ amol




-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 27, 2005 12:53 AM
To: [email protected]
Subject: DO NOT REPLY [Bug 33250] - Out of Memory Error while Stress
Testing


DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33250>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33250


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From [EMAIL PROTECTED]  2005-01-27 06:52 -------
What was max heap size? 2GB?

In any case, a POI HSSF workbook takes a substantial amount of memory.
Reading
and writing take additional memory since it has to be done in-memory.
Therefore,
Out of Memory in concurrent access cannot be considered a bug. If, however,
you
find memory LEAKS (ie, all memory should be reclaimed by the GC AFTER you
loose
a reference to a workbook) then that is certainly a bug. 

There is, of course, a long running feature request to reduce memory usage,
but
that's waiting for contributions!

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/

Reply via email to