Note
This documentation is for a prior release of Kinetica. For the latest documentation, click here.
The following is a complete example, using the Python API, of a CUDA-based UDF that performs various computations using the scikit-CUDA interface. It will take two vectors and one matrix of data loaded from a Kinetica table and perform various operations in both NumPy & cuBLAS, writing the comparison output to the system log.
This setup assumes the UDF is being developed on the Kinetica host (or head
node host, if a multi-node Kinetica cluster); and that the Python database
API is available at /opt/gpudb/api/python
and the Python UDF API is
available at /opt/gpudb/udf/api/python
. This setup also assumes a local
CUDA installation at /usr/local/cuda
.
This example will contain the following Python scripts (click to download):
- udf_cublas_py_init.py : creates the schema & input table and loads test data
- udf_cublas_py_proc.py : the UDF itself
- udf_cublas_py_exec.py : creates & executes the UDF
The CUDA Toolkit is a pre-requisite for this example. Visit nVidia for details.
Note
All commands should be run as the gpudb
user.
The Scikit-CUDA package is also required and must first be installed.
|
|
|
|
After copying the three example scripts to a gpudb
-accessible
directory on the Kinetica head node, the example can be run as follows,
specifying the database URL, username, & password to the Python scripts:
|
|
The results of the UDF run can be seen in the system log file.
Execution Detail
The UDF will load data upon which calculations will be performed from example_udf_python.udf_cublas_in_table. Results of those calculations will be logged to the system log.
The input table will contain three float columns and be populated with 10 sets of randomly-generated numbers. The output log will contain the results of each operation, first in NumPy and then in cuBLAS, which should match.
udf_cublas_py_init.py
This initialization script creates the schema & input table and populates it using the standard Kinetica Python API outside of the UDF execution framework.
Several aspects of the initialization process are noteworthy:
The external database connection, indicative of the use of the standard Kinetica Python API--the UDF itself will not have this, as it runs within the database:
Connect to the Database1
kinetica = gpudb.GPUdb(host=[args.url], username=args.username, password=args.password)
Schema and input table creation:
Create Schema1 2
SCHEMA = 'example_udf_python' kinetica.create_schema(SCHEMA, options=OPTION_NO_CREATE_ERROR)
Create Input Table1 2 3 4 5 6 7 8 9 10
input_table = gpudb.GPUdbTable( _type = [ ["x", "float"], ["y", "float"], ["z", "float"] ], name = INPUT_TABLE, db = kinetica, options = gpudb.GPUdbTableOptions.default().is_replicated(True) )
udf_cublas_py_proc.py
This is the UDF itself. It uses the Kinetica Python UDF API to perform various mathematical functions against the input table column values and output the results to the system log. It runs within the UDF execution framework, and as such, is not called directly--instead, it is registered and launched by udf_cublas_py_exec.py.
Noteworthy in the UDF are the following:
The initial call to ProcData() to access the database:
Begin UDF1
proc_data = ProcData()
The retrieval of input data values:
Retrieve Input Data Values1 2 3 4 5 6 7 8 9 10 11 12 13
in_table = pd.input_data[0] x = np.ndarray(shape=(in_table.size, 1), dtype=float).astype(np.float32) y = np.ndarray(shape=(in_table.size, 1), dtype=float).astype(np.float32) M = np.ndarray(shape=(in_table.size, 3), dtype=float).astype(np.float32) # Initialize vectors & matrix with database values for i in xrange(0, in_table.size): x[i,0] = in_table['x'][i] y[i,0] = in_table['y'][i] M[i,0] = in_table['x'][i] M[i,1] = in_table['y'][i] M[i,2] = in_table['z'][i]
The final call to complete() to mark the process as finished and ready for clean-up:
End UDF1
proc_data.complete()
udf_cublas_py_exec.py
The execution script uses the standard Kinetica Python API to register the UDF in the database and then execute it.
The registration step associates a name with the UDF execution code contained in udf_cublas_py_proc.py, the command ( python ) and arguments (the name of the proc script) to use to run it, and that it will run in distributed mode.
|
|
The execution step invokes the UDF by name, passing in the input table name against which the UDF will execute.
|
|