Partitioning is used to put table A and table B on different servers to balance the load on the DB. On a Web system, the database is often the bottleneck of the whole system.

As the amount of data in the table rests in the memory of the DB server (equivalent to disk I/O), it creates an increasing a loss of performance. The simplest answer may be to expand the memory (because memory is cheap these days). However, there are various problems with this solution, therefore it may be not as simple as expected first.

It may be possible to increase the DB server itself, and it is worth considering partitioning of the server load. However, this is a difficult issue, server scaling depends on the size of the DB. Many helpful books have been published on this subject. For this reason, I will not discuss this here any further.

The TreeFrog Framework provides a mechanism for partitioning, giving easy access data on a different DB server.

Partitioning by SqlObject

As a prerequisite, we use table A for host A, and table B for host B.

First, make separate database configuration files describing the hosts connection information. The file names must be databaseA.ini and databaseB.ini respectively. They should be located in the config directory. For the contents of the file, write the appropriate values. Here is an example of the way the dev section might be defined.


Next define the file names of the database configuration files in the application configuration file (application.ini). Use DatabaseSettingsFiles with the values written side by side and seperate them by spaces.

# Specify setting files for databases.
DatabaseSettingsFiles=databaseA.ini  databaseB.ini

The database IDs follow the sequence 0, 1, 2, … as per following the example:

  • The database ID of the host A : 0
  • The database ID of the host B : 1

Then, set the header file of SqlObject with this database ID.
Edit the header file that is created by the generator. You can also override the databaseId() method by the returned database ID.

class T_MODEL_EXPORT BlogObject : public TSqlObject, public QSharedData
    int databaseId() const { return 1; }  // returns ID 1

By doing this, queries for BlogObject will be issued to host B. After that, we can just use the SqlObject as in the past.

The example here was made with two DB servers, but is also compatible with three or more DB servers. Simply add the DatabaseSettingsFiles in the configuration file.

Thus, partitioning can be applied without changing the logic of the model and controller.

Querying Partitioned Tables

As discussed in the SQL query, the TSqlQuery is not only used to issue a query on its own, or it doesn’t need to extract all values, but you can use it to apply to the partitioning.

As follows, the database ID is specified in the second argument to the constructor:

TSqlQuery query("SELECT * FROM foo WHERE ...",  1);  // specifies database ID 1

This query is then therefore executed to host B.