To install and run Trados Business Manager Desktop, you need:
- OS: Microsoft Windows 7 or higher
- APS.NET Core Runtime and .NET Runtime (https://dotnet.microsoft.com/download/dotnet/5.0)
- .NET Framework 8 (to run licensing utility)
- CPU and RAM: Any (application takes 300-800 Mb of memory while in use)
- Hard drive: SSD recommended to speed-up database operations
To install and run Trados Business Manager Online, you need:
- OS: Microsoft Windows Server, any version, with Internet Information Services feature installed
- Database engine (Microsoft SQL Server or PostgreSQL)
- APS.NET Core Hosting Bundle (https://dotnet.microsoft.com/download/dotnet/5.0)
- .NET Framework 8 (to run licensing utility)
- CPU and RAM: Any. Take a note here that each additional user creates additional load for CPU and RAM. The more concurrent connections, the more requests are sent to database, which CPU has to process. However, in general, if your server can run Windows Server, it can run TBM with around 10-30 users. However, in fact it could appear that it supports hundreds of users, and actual performance data can be gathered while testing TBM in a real scenario.
- Hard drive: SSD recommended to speed-up database operations
When you run Trados Business Manager for the first time (clean installation), you will be prompted to enter a password. By default, user name is Admin, and password is User@TBM. After logging in, you can go to the Security > Users, select Admin user and change its password.
TBM Team performance test results
Based on internal tests performed using different configurations, we have certain findings described below.
First of all, it is critically important to not to disable Connection pooling in database connection strings. If you don't include any connection pooling parameters in the connection string (for example, Max Pool Size), then application will automatically enable connection pooling and set max pool size to 1000. Each user connected to the application in any point of time will use 1 slot in the connection pool.
CPU | RAM | Database engine | Number of momentum concurrent users | Approximate number of supported users | Average loading time of 2 most used pages (Dashboard then Job list) | CPU loading | Memory usage |
Intel Xeon E5-2630 2.2 GHz (4 logical cores) | 8 GB | PostgreSQL | 200 (each new user connects after 0.5 secs after previous user) | 300 | 10-20 sec | about 50% | About 2 Gb |
Intel Core i7-9750H 2.6 GHz (12 logical threads) | 32 GB | Microsoft SQL Server (recommended!) | 200 (each new user connects after 0.5 secs after previous user). We were not able to conduct test with larger amount of users, because each user requires to run browser instance, and there was not enough local resources to do that. When we'll manage to conduct a test with 1000 users, we'll update this table. | 1000 | 8-15 sec | about 30% | About 2 Gb |
Take a note that these are only estimated numbers, and they don't create any commitment, because real performance will depend on your database size and other applications running on a server. Also, in real scenario users don't navigate between pages each 0.5 secs - this period is usually greater (about 1-3 secs of not greater).