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.

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

clfft issues #54

Open
tdd11235813 opened this issue Nov 18, 2016 · 5 comments
Open

clfft issues #54

tdd11235813 opened this issue Nov 18, 2016 · 5 comments
Assignees
Labels

Comments

@tdd11235813
Copy link
Contributor

  • CPU only: 4096 with Inplace_Real and Outplace_Real yield CL_OUT_OF_RESOURCES when executing the backward plan (also reproduced it with a pure clfft code) (8192 or 2048 are working)
  • it seems clfft is leaking memory
  • I cannot handle clfft and out-of-memory kills, so I have to cap the input sizes to get the results in time
@tdd11235813 tdd11235813 self-assigned this Nov 18, 2016
@psteinb
Copy link
Contributor

psteinb commented Nov 18, 2016 via email

@tdd11235813
Copy link
Contributor Author

the problem is, that the amount of leaked memory grows with input size and number of inputs. This explains why I could not handle the OOM kills after a while.
For some results for our draft I would separate the dimensions as I have done with fftw (1D, 2D and 3D have separate output csv files). If time allows, I prepare tomorrow a version for clfft folks.

@psteinb
Copy link
Contributor

psteinb commented Nov 24, 2016

AFAIK, this was fixed with #55 ?

@tdd11235813
Copy link
Contributor Author

yeah, I put an upper limit in #55, since clfft officially supports sizes to something 2^24.
The 4096 and the mem-leak is an open issue, see issue 171 and 172

@psteinb
Copy link
Contributor

psteinb commented Nov 25, 2016 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants