Re: SISC on Android and the Heap

"Scott G. Miller" <[email protected]> Mon, 1 Mar 2010 10:25:36 -0600
Newsgroups gmane.comp.java.sisc.user
Message-ID <[email protected]>
--===============7888448293251909233==
Content-Type: multipart/alternative; boundary=005045013fa4f7baa40480bfb25d

--005045013fa4f7baa40480bfb25d
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Feb 28, 2010 at 6:22 PM, Chad Albers <[email protected]> wrote:

> I've been plugging away on getting SISC to work on Android, and made more
> progress.  But I've hit a major obstacle: serialization and deserialization
> is notoriously slow on Android.  Really slow.  Embedded inside a Android
> App, SISC takes about 45 seconds to run a simple eval on the emulator.  Most
> of that time is spent on (initialize) - which performs a lot of
> deserialization on the precompiled heap file.
>
> My question is can I operate SISC in some way without using the precompiled
> heap, and instead loading in the code precompiled in the heap.  Scott
> Miller's 2002 paper seems to imply that this is possible, provided you're
> willing to take a 10-15 sec performance hit (page 5).
>
>
The alternative to the heap is to load all the startup code from scratch,
which is way slower (by about an order of magnitude).   It may be possible
however to sacrifice some space (ie a bigger heap) and use a different
encoding.  Does the Android platform have a profiler?  Seeing where the bulk
of the time is spent during startup may help suggest a different heap
storage strategy.


> Even if I manage this task, my next question is how often does SISC use
> serialization/deserialization during processing...(I suspect a great deal).
>
>
Code is lazily loaded in using ser/deser during operation, yes, but the bulk
of R5RS is available when you hit the prompt.

Scott

--005045013fa4f7baa40480bfb25d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sun, Feb 28, 2010 at 6:22 PM, Chad Albers <span dir=3D"ltr">&lt;<a href=
=3D"mailto:[email protected]">[email protected]</a>&gt;</span> wrot=
e:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padd=
ing-left: 1ex;">
I&#39;ve been plugging away on getting SISC to work on Android, and made mo=
re progress. =A0But I&#39;ve hit a major obstacle: serialization and deseri=
alization is notoriously slow on Android. =A0Really slow. =A0Embedded insid=
e a Android App, SISC takes about 45 seconds to run a simple eval on the em=
ulator. =A0Most of that time is spent on (initialize) - which performs a lo=
t of deserialization on the precompiled heap file.=A0<div>

<br></div><div>My question is can I operate SISC in some way without using =
the precompiled heap, and instead loading in the code precompiled in the he=
ap. =A0Scott Miller&#39;s 2002 paper seems to imply that this is possible, =
provided you&#39;re willing to take a 10-15 sec performance hit (page 5).</=
div>

<div><br></div></blockquote><div><br>The alternative to the heap is to load=
 all the startup code from scratch, which is way slower (by about an order =
of magnitude).=A0=A0 It may be possible however to sacrifice some space (ie=
 a bigger heap) and use a different encoding.=A0 Does the Android platform =
have a profiler?=A0 Seeing where the bulk of the time is spent during start=
up may help suggest a different heap storage strategy.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px so=
lid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div=
></div><div><div><div>Even if I manage this task, my next question is how o=
ften does SISC use serialization/deserialization during processing...(I sus=
pect a great deal).</div>
<div><br></div></div></div></blockquote><div><br>Code is lazily loaded in u=
sing ser/deser during operation, yes, but the bulk of R5RS is available whe=
n you hit the prompt. =A0 <br><br>Scott<br></div></div>

--005045013fa4f7baa40480bfb25d--


--===============7888448293251909233==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--===============7888448293251909233==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sisc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisc-users

--===============7888448293251909233==--