-
Notifications
You must be signed in to change notification settings - Fork 944
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
[WIP]MAHOUT-1974 (dense cuda multiplication) #318
base: CUDA
Are you sure you want to change the base?
Conversation
andy@micheal:~/sandbox/mahout_cuda/cuda$ export SIZE_N=5000 andy@micheal:~/sandbox/mahout_cuda/cuda$ export SIZE_M=5000 andy@micheal:~/sandbox/mahout_cuda/cuda$ export SIZE_S=5000 andy@micheal:~/sandbox/mahout_cuda/cuda$ export DENSITY=.2 andy@micheal:~/sandbox/mahout_cuda/cuda$ export NUM_RUNS=2 andy@micheal:~/sandbox/mahout_cuda/cuda$ export SEED=1234
… into AP-UNIT-TEST
…nto MAHOUT-1974
…ly ending branch here
… needs to repacked mahout in-core matrices (row-major) as column major per the wrapped call to NVIDIA cublasDgemm operation. The fact that cusparse uses CSR rather than CSC is somewhat confusing in this case (for e.g. a Dense %*% Sparse JVM level operation
… need to use transposes. need to check values in unit tests, and transpose in dgemm call as needed
need to rebase |
dce10d7
to
961aee9
Compare
@nsakharnykh @pat @rawkintrevo FYI |
Fixed dense-dense path for JCuda, also switched to JCublas2 interface
@nsakharnykh sorry for the state of this branch, I tend to commit a lot on this project, and leave a lot of [WIP]s in when jumping around to other branches. Resolved all conflicts the against CUDA branch.. going to start looking at Dense %*% sparse again. First need to read up on |
@nsakharnykh I think that I'll fix the routing on this and test the sorted CSC requirement (MAHOUT-2004 and MAHOUT-2003) and then after some cleaning on this, we should push to mahout/CUDA. |
Purpose of PR:
Please give a short description of what this PR is for.
Important ToDos
Please mark each with an "x"
If all of these things aren't complete, but you still feel it is
appropriate to open a PR, please add [WIP] after MAHOUT-XXXX before the
descriptions- e.g. "MAHOUT-XXXX [WIP] Description of Change"
Does this change break earlier versions?
Is this the beginning of a larger project for which a feature branch should be made?