Using this TrackStudio Massive, you can quickly generate a database with the necessary configuration and structure, then check the TrackStudio performance rate for that database and your hardware. The database is created in the TrackStudio XML export format. For importing, use TrackStudio Server Manager (sman) included in TrackStudio SA. 

The following files are used for generating databases: 

• database.ftl – the file with the database template. You should not modify this file in most cases.
• somefile.properties – the file describing the configuration of the database being generated. default.properties is used when a filename is not specified.

Before you begin, the configuration file and the database template must be in one directory with ts-massive.jar

>java -Xmx512m -jar ts-massive.jar

The process will result in an XML file in the TrackStudio export format. 

To generate a database, do the following: 

• Run TrackStudio Server Manager.
• Setup a database connection by choosing the Database Connectivity tab.
• Choose the Database Management tab, enter the XML file name and press the Create Database button.

To login as an administrator, use login=root, password=root. Other users have logins of the following type: user2, user3, etc and password root.

When you run TrackStudio for the first time, it indexes all tasks for full text search. The process of indexing can take up to 30 minutes. If you are not going to use full text search, you can skip the indexing process. To do this before running TackStudio, create the file skipindex.flag in the directory that is specified in the trackstudio.indexDir parameter in trackstuido.properties.

The configuration file looks like this:

# TrackStudio Massive configuration

# Database template name (‘default.ftl' by default)
template=database.ftl

# Output export file (‘output.xml' by default)
output=small.xml

# Number of tasks (2500 by default)
tasks 2500

# Number of messages (10000 by default)
messages 10000

# Number of users (10 by default)
users 10

# Task distribution factor. Must be greater than 1
# and less than the specific number of tasks.
# The greater task_factor is, the more subtasks top
# level tasks will have and the wider and
# shallower the task tree will be. The default is 10
task_factor 10

# User distribution factor. Must be greater than 1 and
# less than the number users. The greater user_factor is,
# the more subordinated users will be created.
# The default is 10
user_factor 10

# Message distribution factor. Must be greater than 1 and
# less than the amount of tasks. The more message_factor is,
# the more evenly messages will be distributed among tasks.
# The default is 10
message_factor 10