Tekla PowerFab Running Slow
Not version-specific
Tekla PowerFab
Tekla PowerFab GO
There are a variety of factors that contribute to Tekla PowerFab running slow. For this article, running slow is defined as excessive time: to open modules such as production control jobs or purchase orders, generate reports, apply/save changes to items, etc. and experienced by multiple users. Therefore, this does not apply if an individual user is experiencing slowness or specific error messages. Below is a list of topics to investigate for possible issues; be sure to explore the linked articles as these expand on critical topics:
Server And Network Configuration
Server
We recommend using an on-premise server and ethernet connection to client computers. A virtual machine’s performance is going to be inherently slower than an equivalent on-premise server; a high-speed internet connection and sufficient computing resources are crucial for performance in this case. For both on-premises and VM ensure the available computing resources meet the Recommended Server Specifications. Solid State Drives are crucial for best performance.
Consider other programs running on the server that may be consuming resources; meaning, you may need additional RAM or processing power, exceeding the recommendations, to accommodate running both PowerFab and another program simultaneously.
Network Interface:
Shop equipment is notorious for interfering with network connections. Typically these interferences are temporary — can be only when the equipment is running (idle or actively being used). Wireless connections are most susceptible to being interfered with, but both wired and wireless connections experience it. Try to reduce communication paths that travel next to or through high voltage equipment. All wired connections should be shielded.
Network Connection:
The server and client computers should be connected via ethernet to the network for best performance. If this is not possible, recognize that even a moderate WiFi connection may have trouble keeping up with the data communication to the server.
Antivirus:
We recommend excluding the MySQL and Tekla PowerFab folders from virus scans. We have found that many antivirus programs will interfere with the creation and transfer of data taking place within those folders. This can have a significant impact on performance. If you wish to scan these folders, this should be done by only allowing scans at specific times, ideally outside of business hours and not during a database backup or any automated events.
The default locations are listed below. The location could be different, as it depends on the file path selected at installation.
C:\mysqlC:\Program Files (x86)\Tekla\Tekla PowerFaborC:\Program Files\Tekla\Tekla PowerFab
Network Connection:
The server and client computers should be connected via ethernet to the network for best performance. If this is not possible, recognize that even a moderate WiFi connection may have trouble keeping up with the data communication to the server.
Job/Inventory Maintenance
A crucial aspect to keeping your database operating efficiently is managing unnecessary clutter. Using Job Maintenance close jobs that are no longer active. This function does not delete jobs; they are simply hidden behind a filter. This should be done in all modules.
Additionally, inventory should be kept up to date and items that have been consumed should be taken from stock (TFS).
Automated Events
We recommend running all automated reports, backups, and optimize database tables outside of business hours. Database backups or generating large reports during a workday will significantly slow down the system for the duration of that process. Optimize database tables should run at least once weekly.
PowerFab & MySQL Version
User Volume:
Consider the volume of users at your company and the size of jobs in PowerFab. If your company has many users simultaneously (>20) then we would recommend staying up to date with the latest version of MySQL and the latest service pack for the version of PowerFab of your choosing. Additionally, if the slow performance seems to be isolated to report generation, then upgrading to the 64 bit version of PowerFab will likely improve performance in that area.
Check your my.ini settings for your database and adjust them to allow for larger queries. See the settings below. If you installed the database to the default location, that file should be located here: C:\mysql
innodb_buffer_pool_size=4G
innodb_flush_log_at_trx_commit=2
innodb_file_per_table=1
innodb_lock_wait_timeout=20
innodb_log_buffer_size=128M
innodb_log_file_size=1G
You do not have to stop the MySQL service to make these changes and save the file, but you will have to restart the service for them to take effect.
Check and Repair Tables
If your system is running slow and it’s not due to any of the above issues, there could be a problem with a table in your database, try running a check and repair tables from command prompt.
Test For Packet Loss
Check with your IT Have your IT perform the following in command prompt from client stations running slow. Additionally, your IT may have other applications they prefer to use for checking network latency and consistency:
ping (server IP)/n 10 /l 65500
Example:
ping 192.168.1.1/n 10 /l 65500
Take a screenshot of the results and compare to any client stations that are not running slow.
Conclusion
Once you’ve completed the above steps, if the cause of the performance issue has not been found please provide the below information to Tekla Support for further investigation.
- Server Information:Specifications - RAM, HD or SSD, OS, VM or on Premise
- Network Information:Speed Test Results, WiFi or wired connection
- Antivirus Information:Has PowerFab been added to exceptions/whitelist?
- Automated Events:Are any events scheduled during business hours?
- PowerFab and MySQL Version:Screenshot the “About” window in PowerFab
- Test For Packet Loss:Screenshot results of ping test
Related