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.

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

Hardware spec #96

Closed
vasu-cherlopalle opened this Issue Apr 29, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@vasu-cherlopalle

vasu-cherlopalle commented Apr 29, 2016

Can you please provide the minimum hardware required for Alenka?

@hurdad

This comment has been minimized.

Show comment
Hide comment
@hurdad

hurdad May 2, 2016

Collaborator

x86 CPU
Takes 10GB RAM to build.
CUDA enabled Nvidia GPU with compute compatibility 3.0 or greater

Collaborator

hurdad commented May 2, 2016

x86 CPU
Takes 10GB RAM to build.
CUDA enabled Nvidia GPU with compute compatibility 3.0 or greater

@vasu-cherlopalle

This comment has been minimized.

Show comment
Hide comment
@vasu-cherlopalle

vasu-cherlopalle May 4, 2016

Built Alenka on Mac by making couple of changes.

  • Makefile : to support compute_30
  • cm.cu : to getTotalSystemMemory

Executing alenka is throwing following error. Any thoughts??
screen shot 2016-05-04 at 9 08 07 am

vasu-cherlopalle commented May 4, 2016

Built Alenka on Mac by making couple of changes.

  • Makefile : to support compute_30
  • cm.cu : to getTotalSystemMemory

Executing alenka is throwing following error. Any thoughts??
screen shot 2016-05-04 at 9 08 07 am

@hurdad

This comment has been minimized.

Show comment
Hide comment
@hurdad

hurdad May 4, 2016

Collaborator

typically we load data like this
./alenka -v load_part.sql

I have not tried alenka on OSX, just CentOS 7

Collaborator

hurdad commented May 4, 2016

typically we load data like this
./alenka -v load_part.sql

I have not tried alenka on OSX, just CentOS 7

@vasu-cherlopalle

This comment has been minimized.

Show comment
Hide comment
@vasu-cherlopalle

vasu-cherlopalle Jun 13, 2016

Made necessary changes to resolve the issue. The changes are in the repo.

vasu-cherlopalle commented Jun 13, 2016

Made necessary changes to resolve the issue. The changes are in the repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment