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

[SYSTEMML-1325] Fixes formatting issues and warnings. #838

Closed
wants to merge 1 commit into from

Conversation

thomas9t
Copy link
Contributor

Fixes some minor formatting issues (spaces -> tabs) and warnings from #836 Removes no longer needed code for compilation and execution from org.apache.sysml.api.mlcontext.ScriptExecutor Fixes a bug from #836 that was causing explain plans to not be printed in ML context. @niketanpansare @mboehm7 can you please take a look when you have a chance and let me know if you have any comments?

thomas9t referenced this pull request Oct 19, 2018
Support to JMLC

This PR adds support for compilation and execution of GPU enabled
scripts in JMLC and harmonizes the pipeline used to compile and execute
DML programs across the JMLC, MLContext and DMLScript. Specifically, the
following changes were made:

1. All three APIs now call ScriptExecutorUtils.compileRuntimeProgram to
compile DML scripts. The original logic in MLContext and JMLC for
pinning inputs and persisting outputs has been preserved.
2. All three APIs now use ScriptExecutorUtils.executeRuntimeProgram to
execute the compiled program. Previously, JMLC called the Script.execute
method directly.
3. jmlc.Connection.prepareScript now supports compiling a script to use
GPU. Note that following #832 the issue noted in #830 has been resolved.
4. A PreparedScript is now statically assigned a GPU context when it is
compiled and instatiated. This has potential performance implications
because it means that a PreparedScript must be executed on a specific
GPU. However, it reduces overhead from creating a GPU context each time
a script is executed and unsures that a user cannot compile a script to
use GPU and then forget to assign a GPU context when the script is run.
5. Per (3) I have added a unit test which compiles and executes a GPU
enabled script in JMLC both with and without pinned data and just
asserts that no errors occur.

Closes #836.
@niketanpansare
Copy link
Contributor

Overall, this looks good to me. Let's wait for few days in case @mboehm7 has additional comments.

@thomas9t
Copy link
Contributor Author

thomas9t commented Nov 2, 2018

@niketanpansare anything else we need to do here?

@asfgit asfgit closed this in bf4ba16 Nov 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants