Question

If I only ever use one Statement at a time would it be worthwhile cacheing it along with my Connection. I already cache the connection so I could cache the statement at almost no cost at all.

Essentially I suppose I am asking if there is any cost/overhead to creating a statement. I fully understand the benefits of creating prepared statements. I am talking specifically about Connection.createStatement() here.

Answer 1

Some research into an open-source jdbc driver (jtds) suggests the following object overhead for each Statement created. I am trying to count the cost of creating a new Statement every time I want to query the database rather than holding one single cached one and reusing it:

1. A Connection – Presumably cached so insignificant.
2. A TdsCore – Looks like a protocol implementation but it is cached so insignificant.
3. A ResultSet.
4. An ArrayList of batched items.
5. An ArrayList of open ResultSets.
6. Column meta data.

So it looks like the highest proportion of the cost of Statements involves what is left around by any query that has been run.