You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run program using xmlbeansxx and generated classes (large xsd scheme), whatever I do, memory usage never goes lower than 300k. Is there any way to destroy allocated memory when parsing is not needed anymore?
The text was updated successfully, but these errors were encountered:
this is a hard one :)
(it's getting more and more interesting)
I'm working on a laptop with 6GB of ram, I never thought 300k could be a
problem ;)
can you tell us what are you planning to do with xmlbeansxx ?
The problem is that we do alot of static initialization to speed things up,
and to store
xsd information's.
We also have the class StoreString which statically holds all string used
in a xml.
(to speed up comparison of strings).
But 300k seems like a lot.
Can you please send us the simplest use case and how you made the
measurement ?
When I find time I will look on it.
(Unfortunately, no sooner than the next weekend)
When I run program using xmlbeansxx and generated classes, whatever I do,
memory usage never goes lower than 300k. Is there any way to destroy
allocated memory when parsing is not needed anymore?
Reply to this email directly or view it on GitHub: #9
When I run program using xmlbeansxx and generated classes (large xsd scheme), whatever I do, memory usage never goes lower than 300k. Is there any way to destroy allocated memory when parsing is not needed anymore?
The text was updated successfully, but these errors were encountered: