-
Suggestion
-
Resolution: Duplicate
-
None
-
None
XML Import shouldn't be such a memory hog.
This is an interesting one. As far as I can tell, the XML import loads all entities to memory and then writes all entities to disk. This is all nice and well when there's more RAM than this needed. However, if more memory is required is > allocated then the system stuggles severly / throws an out of memory exception.
Perhaps a better solution would be to do incremental imports rather bulk. This will probably be slower, but at least it will have a more consistent response time and will actually scale for humungous databases.
- duplicates
-
JRASERVER-4622 SAX importer still uses O(n) memory
- Closed