Just a few more points on this fascinating topic.
* The JVM internally represents characters as UTF16.
This means that any ascii text will use twice as much
memory in the JVM as on disk.
* While reading in the file, you will likely do some
copying. Even if you allocate a char[] of the right
Thanks, Thilo, good points!
Another fine point below
Thilo Goetz wrote:
Just a few more points on this fascinating topic.
* The JVM internally represents characters as UTF16.
This means that any ascii text will use twice as much
memory in the JVM as on disk.
* While reading in the file,
Marshall Schor wrote:
Thanks, Thilo, good points!
Another fine point below
Thilo Goetz wrote:
[...]
* On 32-bit windows, a process may use up to 2GB of
memory, not 4GB. Subtract from that the memory that
the JVM needs, and you get to some number around 1.4GB
as the maximum JVM heap
+1
-- Tong
On Sun, Mar 8, 2009 at 8:58 AM, Marshall Schor m...@schor.com wrote:
+1 Contribution looks quite impressive!
-Marshall
Rico Landefeld wrote:
Hi,
I've attached the corrected POM without parent POM to the issue. This
should solve the problem.
best regards,
Rico
[
https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1297.
---
Resolution: Fixed
Uima AS Service Not Handling Send Failures Correctly
[
https://issues.apache.org/jira/browse/UIMA-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1296.
---
Resolution: Fixed
Modified client code to send Stop requests to the same temp queue that handles
