M-Files goes slow so M-Files Import

Hello,

We have two M-Files and SQL servers.

M-Files server :
Processor: 16, Intel(R) Xeon(R) Silver 4310 CPU @2.10GHz
RAM: 64GB
1TB SSD storage

SQL Server Server :
Processor: 16, Intel(R) Xeon(R) Silver 4208 CPU @2.10GHz
RAM: 100GB (80GB For SQL Server)
6TB SSD storage for SQL files

Please note that we use several API requests (Import and Export) as well as M-Files Importer.

You will find below the valut size :

mdf file: 380GB
ndf file: 5TB

Please let me know if we need to increase the configurations.

Best regards,

Parents
  • I'm not sure I really understand what you're asking, Ali.

    I think that you're having performance issues, but I am not sure where or why.  Performance issues are typically difficult to diagnose via the forum as they depend a lot upon many factors to do with your vault structure, hardware, code configuration, etc.  If you work for a partner it may be best to open an Implementation Support Request (via the support portal) to ask for assistance.  If you work for a customer then reach out to your partner.

  • Thank you for your reply.

    Yes, i am partner and i will create a ticket in the support.

    Also just for your information, when i restart servers, M-Files works perfect for one week and after it becomes slow again.

  • Only one thing that comes to my mind; do you store your files in SQL DB ? 5 TB in MDF and/or NDF is a bulky size for M-Files DB that would contain only Metadata Structure and Indexes. 

    If you are storing files in SQL DB, you can move those files out of SQL DB and put them in folders. It should work faster that way..

Reply Children
No Data