Book Image

Practical Automated Machine Learning Using H2O.ai

By : Salil Ajgaonkar
Book Image

Practical Automated Machine Learning Using H2O.ai

By: Salil Ajgaonkar

Overview of this book

With the huge amount of data being generated over the internet and the benefits that Machine Learning (ML) predictions bring to businesses, ML implementation has become a low-hanging fruit that everyone is striving for. The complex mathematics behind it, however, can be discouraging for a lot of users. This is where H2O comes in – it automates various repetitive steps, and this encapsulation helps developers focus on results rather than handling complexities. You’ll begin by understanding how H2O’s AutoML simplifies the implementation of ML by providing a simple, easy-to-use interface to train and use ML models. Next, you’ll see how AutoML automates the entire process of training multiple models, optimizing their hyperparameters, as well as explaining their performance. As you advance, you’ll find out how to leverage a Plain Old Java Object (POJO) and Model Object, Optimized (MOJO) to deploy your models to production. Throughout this book, you’ll take a hands-on approach to implementation using H2O that’ll enable you to set up your ML systems in no time. By the end of this H2O book, you’ll be able to train and use your ML models using H2O AutoML, right from experimentation all the way to production without a single need to understand complex statistics or data science.
Table of Contents (19 chapters)
1
Part 1 H2O AutoML Basics
4
Part 2 H2O AutoML Deep Dive
10
Part 3 H2O AutoML Advanced Implementation and Productization

Understanding what a MOJO is

MOJOs are counterparts to H2O model POJOs and technically work in the same way. H2O can build and extract models trained in the form of MOJOs, and you can use the extracted MOJOs to deploy and make predictions on inbound data.

So, what makes MOJOs different from POJOs?

POJOs have certain drawbacks that make them slightly less than ideal to use in a production environment, as follows:

  • POJOs are not supported for source files larger than 1 GB, so any models with a size larger than 1 GB cannot be compiled to POJOs.
  • POJOs do not support stacked ensemble models or Word2Vec models.

MOJOs, on the other hand, have the following additional benefits:

  • MOJOs have no size restrictions
  • MOJOs solve the large size issue by removing the ML tree and using a generic tree walking algorithm to navigate the model computationally
  • MOJOs are smaller in size and faster than POJOs
  • MOJOs support all types of models trained using H2O AutoML...