Background
==========

I am creating an API utilizing the Bible where I would like to be able to eliminate as much as the database bottleneck as possible. My data is fairly de-normalised to eliminate most unnecessary joins.

Information
===========

**Seeing as the text of the Bible doesn't change**, I will be doing hardly any `INSERT` statements. The only time I will insert data is when I add a new translation, which will happen periodically, but I don't care about the speed here.

**I will, however, be doing *tons* of** `SELECT` **statements.**

I do not need any transnational, ACID compliant features. My primary concern is speed.

The Question
============

What would the ideal MySql storage engine be to fit these conditions?

I am aware of the basics of each engine (my guess would that `MyISAM` is ideal), so I am looking for an answer that can be backed up with statistics or further reasoning demonstrating a deep knowledge of some of these engines.

Although using `NoSQL` may be better than a `RDBMS`, that is not the information I'm looking for.