Cosmo on x86_64

I have a server where I've installed an 64-bit native
version of Debian
sarge.  The 64-bit version of Sun's Java VM appeared to
work fine, but I was
having problems starting Cosmo because "could not
reserve enough space for
object heap".

Turns out that I needed to increase the amount of memory I
allow the Java
process to consume.  In my 32-bit installs, I start Java
with -Xms700m
-Xmx700m and limit (via ulimit) the total process memory to
1.5Gb.  Seems
like plenty.  Keeping the same -Xms and -Xmx settings in my
64-bit install,
I need to increase the memory limit to 2.1Gb before the
process will start.

Why a process with a 700Mb heap needs 2.1Gb to start is a
bit of a mystery.
 The Cosmo "server status" entries show 124Mb
used of 686Mb max.

Interestingly, at 2.0Gb, Java still can't start, but
instead gives an
OutOfMemoryError instead of the "could not reserve
enough space" error.

Other than the weirdness of this need for increased memory,
I can now report
success for Cosmo running on the x86_64 architecture.  Not
very important,
but thought I'd note it here for the archives.
_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo

Hello,

Just roughly speaking, what is Cosmo's current
and targetted minimum system requirements?  Say
for 500 users.

Best Regards,
Kervin



Jared Rhine wrote:
> I have a server where I've installed an 64-bit native
version of Debian
> sarge.  The 64-bit version of Sun's Java VM appeared
to work fine, but I was
> having problems starting Cosmo because "could not
reserve enough space for
> object heap".
> 
> Turns out that I needed to increase the amount of
memory I allow the Java
> process to consume.  In my 32-bit installs, I start
Java with -Xms700m
> -Xmx700m and limit (via ulimit) the total process
memory to 1.5Gb.  Seems
> like plenty.  Keeping the same -Xms and -Xmx settings
in my 64-bit install,
> I need to increase the memory limit to 2.1Gb before the
process will start.
> 
> Why a process with a 700Mb heap needs 2.1Gb to start is
a bit of a mystery.
>  The Cosmo "server status" entries show
124Mb used of 686Mb max.
> 
> Interestingly, at 2.0Gb, Java still can't start, but
instead gives an
> OutOfMemoryError instead of the "could not
reserve enough space" error.
> 
> Other than the weirdness of this need for increased
memory, I can now report
> success for Cosmo running on the x86_64 architecture. 
Not very important,
> but thought I'd note it here for the archives.
> _______________________________________________
> Cosmo mailing list
> Cosmoosafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo
> 

_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo

On 3/2/06, Kervin L. Pierre <kervinadevsoft.com> wrote:

> Just roughly speaking, what is Cosmo's current
> and targetted minimum system requirements?  Say
> for 500 users.

we're still a bit too early on to answer that question
well. about the
best we've done so far is "support 10,000 users, each
with a single
1,000 event calendar, on a single server host". we've
also done some
work to get the disk requirement for that number of users
and events
below one terabyte ;)
_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo

I too am interested in this. What are the specs for what you
mention 
below (10,000 users each with 1,000 events)?


Brian Moseley wrote:
> On 3/2/06, Kervin L. Pierre <kervinadevsoft.com> wrote:
>
>   
>> Just roughly speaking, what is Cosmo's current
>> and targetted minimum system requirements?  Say
>> for 500 users.
>>     
>
> we're still a bit too early on to answer that question
well. about the
> best we've done so far is "support 10,000 users,
each with a single
> 1,000 event calendar, on a single server host".
we've also done some
> work to get the disk requirement for that number of
users and events
> below one terabyte ;)
> _______________________________________________
> Cosmo mailing list
> Cosmoosafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo
>   

_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo