Database optimization for trades and link report

Important: There is no need for you to play with this feature if your server is not overloaded.

By default database processing cycle set to 1 min for trade database (full hourly details, not optimized) and 60 min for link report database (fully optmized, no hourly details). If the trade database processing is set to 1, database gets processed each minute and the hourly database structure contains 60 parts (1 part for each minute - maximum details). This database is 60 times larger than a database with processing set to every 60 mins.

Longer cycles: number of database operations reduced, database size reduced. Smaller database means less reads/writes from the hard drive, which is very important. Reading/writting large amount of data from the hard driver is often the cause for a high server load. The only downside is, if you set longer cycles for "trade database" you will see less hourly details in the statistics / details menu and on the graphs. If you set longer cycles for the "link database" you will see less hourly details in the statistics / links menu.

Shorter cycles: more database operations, larger database size. You will be able to see more hourly details, but the database size will be larger and processing will consume more server resources.

Trade database: Since the trade database is more important than the link database, the cycles should be shorter. Recommended values: 1 - 15 (default 1).

What does "less details because of the longer cycles" mean: E.g. if you will increase trade database processing cycle from 1 to 10 minutes, trade database will shrink for 10 times and it will only be processed 6 times per hour (60 / 10 = 6). If you will try to view detailed hourly statistics in the statistics / details menu (or graphs), you will see that you can set "split" parameter in the "select" table to maxium 6 parts. You will be able to split hourly details to 6 parts (instead of 60) only.