| Summary: | Out of Memory Error while Stress Testing | ||
|---|---|---|---|
| Product: | POI | Reporter: | Sumit Machwe <sumit_machwe> |
| Component: | HSSF | Assignee: | POI Developers List <dev> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.5-FINAL | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
|
Description
Sumit Machwe
2005-01-26 18:02:49 UTC
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! 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! |