Thus spake "Kustaa Nyholm":
> Thanks Greg,
>
> for a very thorough treatment on the subject. As I feared, quite a lot
> work
> and testing to do just to the let user set the heap size! I think I'll
> wait for a few years to see if things will improve...
>
> In any case, it is nice to have all this as broadly as you presented
> here stored in the list archieves for later reference if me or
> someone else decide to go forward and implement this.
>
> br Kusti
>
I faced a similar problem a while back. The app I'm working on has a
natural separation between the manager and player components. The
manager is a window which shows you a module library, and by itself
uses very little heap. The player is a window where a module is loaded,
and needs quite a lot of heap.
The solution I adopted was to store heap preferences for each module,
and launch each player in a separate JVM instance from the manager
using ProcessBuilder. There's very little memory hit for launching
additional JVMs (as they're able to share some memory among them), and
subsequent JVMs start very rapidly. ProcessBuilder lets me launch the
player instances in the same way on all platforms. As an added feature,
the players aren't competing with each other for heap space this way (it's
possible to have more than one player open at once).
--
J.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
