THE INFORMATION IN THIS ARTICLE APPLIES TO:
Why is SiteConfig database file in v8 twice as big as ftp.cfg was in previous versions?
Starting in EFT v8.0, we are using a different way of storing data, putting all Site configuration in one SQLite DB file. SQLite format itself is much larger than ftp.cfg for the same amount of data. All of the data for a Site is stored in a single db file, whereas previously we had several separate storage files: ftp.cfg+workspaces+clients db, etc. In general, the file size is not a problem and doesn't affect speed or performance.
Are there any potential bottlenecks that may now be introduced because of the large database file?
For *normal* EFT usage we don't see any bottlenecks. However, if a client is NOT following recommendations regarding EFT limits for users and virtual folders, some side-effects are possible. In the case of large numbers of users and virtual folders, EFT should be running in a fast and powerful environment, on a powerful, multiple-CPU server computer. Keep in mind that any attempt to connect to a network share that is outside of the EFT environment can slow down the process. Also, SQLite has a cache mechanism that keeps data in memory to avoid frequent disk read operations.