Hi Nil,

Thank you so much for that piece of information. Yes, Indeed! the machine
seems to prefer that I specify the memory resources allocated.

Best,
Austin

On Thu, Mar 14, 2019 at 6:21 AM 'Nil Geisweiller' via opencog <
[email protected]> wrote:

> Hi Austin,
>
> opencog (with the exception of MOSES that takes a crazy 4GB due to
> template overuse) can be compiled on a RPi 2 (1GB of RAM), so it's weird
> that it doesn't compile on your instance. I can recall AWS EC2 being
> prone to memory issues due to disabled swap, but never during compiling.
>
> Maybe look into using ulimit or gcc -ftime-report as suggested here
>
> https://stackoverflow.com/questions/12964013/reducing-memory-allocation-gcc-command#12964053
>
> Nil
>
> On 3/13/19 6:06 PM, Vitaly Bogdanov wrote:
> > Hi Austin,
> >
> > My machine has 16 Gib of RAM, 5 of them are occupied by operating system
> > almost constantly. At least it is enough to build opencog. I have just
> > make a test and I didn't see more than 2 GiB were used during build.
> > Have you tried executing "free" command to see how much of free memory
> > do you have?
> >
> > Best regards,
> >    Vitaly
> >
> >
> > On Tuesday, March 12, 2019 at 7:54:06 PM UTC+3, Austin wrote:
> >
> >     Hi,
> >
> >     After reinstalling and recompiling for the new updates. In running
> >     make for the atomspace. I get errors such as virtual memory
> >     exhausted: Cannot allocate memory.Find attached the error images in
> >     detail.
> >
> >     Please what could cause this; The AWS EC2 instance type used is
> >     t3.large. Also, I am wondering if any specific recommendations of
> >     memory size required to run all of opencog efficiently ?
> >
> >     Greatly appreciate any help provided.
> >     Thank you!
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "opencog" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to [email protected]
> > <mailto:[email protected]>.
> > To post to this group, send email to [email protected]
> > <mailto:[email protected]>.
> > Visit this group at https://groups.google.com/group/opencog.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/opencog/18e0a808-96d2-4740-8213-c115a8a7255a%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/opencog/18e0a808-96d2-4740-8213-c115a8a7255a%40googlegroups.com?utm_medium=email&utm_source=footer
> >.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "opencog" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/opencog.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/opencog/712d88bb-cf4d-081f-f989-a9f6a6d09379%40gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"opencog" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/opencog.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/opencog/CADbdzdyk2-hvS3ircdzJYJSSim16JqyJQitafnNKeqAvW8oMrw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to