Passa ai contenuti principali

Using Rapids cuDF in a Colab notebook

During last Spark+AI Summit Europe 2019 I had a chance to attend a talk from Miguel Martinez who was presenting Rapids, the new Open Source framework from NVIDIA for GPU accelerated end-to-end Data Science and Analytics.


Fig. 1 - Overview of the Rapids eco-system

Rapids is a suite of Open Source libraries:

  • cuDF
  • cuML
  • cuGraph
  • cuXFilter

I enjoied the presentation and liked the idea of this initiative, so I wanted to start playing with the Rapids libraries in Python on Colab, starting from cuDF, but the first attempt came with an issue that I eventually solved. So in this post I am going to share how I fixed it, with the hope it would be useful to someone else running into the same blocker.
I am assuming here you are already familiar with Google Colab. I am using Python 3.x as Python 2 isn't supported by Rapids.
Once you have created a new notebook in Colab, you need to check if the runtime for it is set to use Python 3 and uses a GPU as hardware accelerator. You can check and eventually set it from the toolbar menu Runtime -> Change runtime type. Then you have to check that Colab has given you access to a NVIDIA Tesla GPU, as it is supported by Rapids. You can do this check from the notebook code by running

!nvidia-smi

and look for the GPU type, as highligthed in figure 2:

Fig. 2 - The output of the nvidia-smi command in a Colab notebook

The next step would be the installation of the cuDF library for CUDA 10.x. You can use pip from the notebook:

!pip install cudf-cuda100

At the end of the installation, before importing the cuDF package, you need to do an extra setup that I am going to explain below. If you don't do it, any time you try to execute the cuDF API, you will receive the following misleading error:

Fig. 3 - The error message in Colab when trying to use the cuDF API

The message states that the cudatoolkit isn't installed in your environment, so the numba package cannot be find, which isn't true, as cudatoolkit is already part of the Colab environment. The real root cause of this error is that the paths to the drivers are different in the runtime from what expected by the library. So you have to locate them first

dev_lib_path = !find / -iname 'libdevice'
nvvm_lib_path = !find / -iname 'libnvvm.so'


and setup the environment accordingly

import os

if len(dev_lib_path) > 0:
    os.environ['NUMBAPRO_LIBDEVICE'] = dev_lib_path[0]
else:
    print('The device lib is missing.')
if len(nvvm_lib_path) > 0:
    os.environ['NUMBAPRO_NVVM'] = nvvm_lib_path[0]
else:
    print('NVVM is missing.')


I have also put extra checks in case the paths shouldn't be found, which would probably be useless, but you never know :)

Now you can import cuDF, numpy and any other Python package you would need

import cudf
import numpy as np
...


and start playing with GPU Data Frames

df = cudf.DataFrame()
...


Enjoy it!

I will share my impressions on this library and the others in Rapids as soon as I have completed some PoCs.

Commenti

  1. Feedback from Miguel Martinez (NVIDIA): by installing cuDF using pip, you will get the release 0.61. In order to install a latter or the latest release you have to use conda onstead. Thanks Miguel for the heads up.

    RispondiElimina
  2. This video helps me to understand Matplotlib whats your opinion guys.

    RispondiElimina

Posta un commento

Post popolari in questo blog

Exporting InfluxDB data to a CVS file

Sometimes you would need to export a sample of the data from an InfluxDB table to a CSV file (for example to allow a data scientist to do some offline analysis using a tool like Jupyter, Zeppelin or Spark Notebook). It is possible to perform this operation through the influx command line client. This is the general syntax:

sudo /usr/bin/influx -database '<database_name>' -host '<hostname>' -username '<username>'  -password '<password>' -execute 'select_statement' -format '<format>' > <file_path>/<file_name>.csv

where the format could be csv, json or column.
Example:

sudo /usr/bin/influx -database 'telegraf' -host 'localhost' -username 'admin'  -password '123456789' -execute 'select * from mem' -format 'csv' > /home/googlielmo/influxdb-export/mem-export.csv

Evaluating Pinpoint APM (Part 1)

I started a journey evaluating Open Source alternatives to commercial New Relic and AppDynamics tools to check if some is really ready to be used in a production environment. One cross-platform Application Performance Management (APM) tool that particularly caught my attention is Pinpoint. The current release supports mostly Java applications and JEE application servers and provides support also for the most popular OS and commercial relational databases. APIs are available to implement new plugins to support specific systems. Pinpoint has been modeled after Google Dapper and promises to install agents without changing a single line of code and mininal impact (about 3% increase in resource usage) on applications performance.
Pinpoint is licensed under the Apache License, Version 2.0.

Architecture Pinpoint has three main components:
 - The collector: it receives monitoring data from the profiled applications. It stores those information in HBase.
 - The web UI: the front-end to consum…

Load testing MongoDB using JMeter

Apache JMeter (http://jmeter.apache.org/) added support for MongoDB since its 2.10 release. In this post I am referring to the latest JMeter release (2.13).
A preliminary JMeter setup is needed before starting your first test plan for MongoDB. It uses Groovy as scripting reference language, so Groovy needs to be set up for our favorite load testing tool. Follow these steps to complete the set up:
Download Groovy from the official website (http://www.groovy-lang.org/download.html). In this post I am referring to the Groovy release 2.4.4, but using later versions is fine.Copy the groovy-all-2.4.4.jar to the $JMETER_HOME/lib folder.Restart JMeter if it was running while adding the Groovy JAR file. Now you can start creating a test plan for MongoDB load testing. From the UI select the MongoDB template (File -> Templates...). The new test plan has a MongoDB Source Config element. Here you have to setup the connection details for the database to be tested:



The Thread Group associated with…