Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

tests: recheck memory requirements for x64 host #55

Closed
sergey-dryabzhinsky opened this issue Apr 13, 2017 · 11 comments
Closed

tests: recheck memory requirements for x64 host #55

sergey-dryabzhinsky opened this issue Apr 13, 2017 · 11 comments

Comments

@sergey-dryabzhinsky
Copy link
Contributor

To build LiO on amd64 Debian 8 machine we need more than 6Gb memory.
@aalaesar
Copy link
Contributor

Hi @Sergey,
What happen if there is less than 6GB ? Drop in performances ?
Actually, my tests are run on a debian 8 amd64 vhost with 4GB of ram.

@sergey-dryabzhinsky
Copy link
Contributor Author

My build just breaks with "Killed" and "oops" in syslog.

May be it is because --enable-lto configure option.
LTO can be memory eater.

@sergey-dryabzhinsky
Copy link
Contributor Author

My build killed on CVE tests.
So I disabled them.

@aalaesar
Copy link
Contributor

aalaesar commented Apr 18, 2017 •
edited
Loading

So did it fixed it ?
what was the option in ./configure ?

@sergey-dryabzhinsky
Copy link
Contributor Author

I'm checking that right now. Still compiling.
As for option it was --disable-cve-tests.

@sergey-dryabzhinsky
Copy link
Contributor Author

Nope. 4G not enough to build with LTO.
I'll try again without --enable-lto.

@sergey-dryabzhinsky
Copy link
Contributor Author

Yes, 4Gb enough to build W/O LTO.

So if you will not use --enable-lto configure option then 4Gb will be alright.

@aalaesar
Copy link
Contributor

Does LTO stand for "Linear Tape-Open" ?

@sergey-dryabzhinsky
Copy link
Contributor Author

Nope, it's Link Time Optimization: https://gcc.gnu.org/wiki/LinkTimeOptimization

@aalaesar
Copy link
Contributor

Ok thank you 😄 👍

@sergey-dryabzhinsky
Copy link
Contributor Author

No issue here. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sergey-dryabzhinsky @aalaesar