[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: why are Epic files read using a separate process (JVM)
From: |
Dmitry . Nadezhin |
Subject: |
Re: why are Epic files read using a separate process (JVM) |
Date: |
Thu, 23 Jul 2009 09:06:39 +0400 |
> However, there is a preference which controls either to use
> separate process or main JVM.
I'm sorry. I see at the code that there WAS such a preferences.
-Dima
----- Original Message -----
From: address@hidden
Date: Thursday, July 23, 2009 8:55 am
Subject: Re: why are Epic files read using a separate process (JVM)
> Epic files are large.
> Epic reader in the main process used to throw out of memory
> exception on 32-bit JVM.
> So there is an option to run Epic reader in other process. The main
> JVM keeps in memory only directory
> of signals. Waveforms are stored in a temporary file and are loaded
> by demand.
>
> However, there is a preference which controls either to use
> separate process or main JVM.
>
> -Dima
>
> ----- Original Message -----
> From: Adam Megacz <address@hidden>
> Date: Thursday, July 23, 2009 0:04 am
> Subject: why are Epic files read using a separate process (JVM)
>
> >
> > I'm curious: why does Electric spawn a separate process
> > (EpicReaderProcess) in order to read in Epic files? Why not do it
> > from within the main process?
> >
> > - a
> >
> >
> >
> > _______________________________________________
> > Bug-gnu-electric mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/bug-gnu-electric
> >
>
>
>
> _______________________________________________
> Bug-gnu-electric mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-gnu-electric
>