Sometimes it can be useful to conduct a speed test in order to benchmark read / write speed in a database. This is useful when attempting to diagnose a performance problem on a specific database within different environments. By running the speed test within the current environment and then running the same test on the same database outside of that environment you maybe able to determine that the problem is associated with a resourcing issue within the current environment and is therefore not something associated with the database itself.
This simple speed test inserts 500 item records and displays the elapsed time taken. It then deletes those records and displays the elapsed time taken to perform this process.
It should be noted, that deletions of records always take longer that inserts, so both time will vary.
By copying the database to your own machine eliminates the current environment. Be aware that the spec of the machines (eg: Ram, Disk type (SSD etc) will affect performance, so this must be taken into account when comparing results.
This speed test in in the form of a Command script.
Related Articles
Increasing Firebird Performance
Below are links to two articles relating to potentially increasing Firebird Performance https://ib-aid.com/en/articles/how-to-make-firebird-work-20-faster-at-windows-server-2016-in-less-than-1-minute/ ...
Improving Performance of Opening Lists
As a database gets larger, the opening List grids can take longer to load, when 'Include Closed' Orders, 'Include Updated Status' or 'Include Fully Paid' is turned on along with Filtering and Sorting from the Grid options. This is because in order to ...
Database Sweep Interval Setting To Improve Performance
Amending the Database Sweep Interval Setting Overview: On some large databases, performance issues maybe experienced due to the database Sweep Interval setting being set at a higher level than need be. By default the Sweep Interval setting is set to ...
Ostendo running slowly
Some of the most common factors that could influence speed are: 1) Firebird database needs to be backed up & restored (effectively fixes indexing or data issues) 2) The server is not optimised as a database server (i.e. the disk configuration is ...
Archiving Historical Journal Records
When we post to Accounting products like MYOB AR Live, Xero, QBO and Sage Evolution, we post from 4 tables in Ostendo. JOURNALHEADER (these records will be posted as General Ledger Journals in the Accounting Software) JOURNALLINES (each journal may ...