Re: Memory allocation problem?

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0179490477==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigDF9FF66F3861745FE84FE04A"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigDF9FF66F3861745FE84FE04A
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi James,

SableVM uses a stop/copy collector.  This has advantages and drawbacks.

Main advantages:
- It is a precise collector.  All "unreachable" objects are collected.
  This is not always the case in Kaffe, for example.
- It doesn't suffer any Java heap memory fragmentation.  This means that
  a very long running process won't endup being unable to use available
  memory because it is too fragmented.

Main disadvantage:
- It only uses 50% of heap space, as it uses the other 50% as a target
  while copying objects during collection.
- It is not a hybrid/generational collector as Sun's one.

Now, SableVM can be compiled to use Carl Lebsack's generational
collector.  Unless I'm wrong, I think that all generations are collected
using a copying collector, so this won't necessarily solve your tight
space problem.  I'll let Carl discuss the matter, if you have additional
questions on this collector.

I am puzzled, though...  Don't you have more "virtual memory" than
physical memory (i.e. RAM)?  Usually, applications are limited by the
amount of available virtual space, not by RAM.

Etienne

Eunseok, Kim wrote:
> I increased VmWare memory to 1024M, then the allocation of matrix was
> successful.
>=20
> =91 kaffe =96 Xmx 1024m Benchmark 10000 1 =92 works well.
>=20
> Why does sablevm require larger memory than other jvm?
>=20
> Is this related memory option?
>=20
> I still don =92 t know why sablevm does not work in 256M memory.
>=20
> If anybody know it, then please let me know~

--=20
Etienne M. Gagnon, Ph.D.            http://www.info2.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/


--------------enigDF9FF66F3861745FE84FE04A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEfyxGjyrJi4rH84gRAts0AJ481BvEzCcnrYA3YAyrcLUuAgu5BgCfXlnt
8eHfzBBGOy8+wnzUcFvwZjY=
=lLEP
-----END PGP SIGNATURE-----

--------------enigDF9FF66F3861745FE84FE04A--


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

_______________________________________________
SableVM-user mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-user

--===============0179490477==--