Review M-Files on G2 & get a $25 gift card Arrow right Review us!

Options
  • Locked Locked
  • Replies 13 replies
  • Subscribers 8 subscribers
  • Views 758 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Slow XML import

Former Member
Former Member
Hia,

We have a conversion mechnism running that's converting legacy postscript output to generic PDF with formatted XML (1 pdf = 1 pdf, same naming).
On a daily base about 5000 files are generated and imported with an external file source job using the XML and xpaths for meta data.
It's all working nicely, however, the import into M-Files is so slo...o..w.....

Any experience here to speed up this process, to increase the # of files per import (for example 500 in stead of 100) etc?
The (virtual) hardware shouldn't be the issue, nor the SQL vault database.

We have a backlog of let's say a few million files, so any speed increase would be great.


PS: best wishes all!
Parents
  • Former Member
    Former Member
    something strange.

    I manually duplicated the import job to a job_2. Everything is exactly the same, except for the name_2 and the source folder_2 (which is also local just like first job).

    So now I have the jobs: Import_Converted_Files & Import_Converted_Files_2

    The second job_2 imports like 5-10 times faster than the first job. Exactly the same files, meta data etc.
    How??

    Is M-Files doing something funny with the external source name property? It feels like that there is some form of ever growing registry causing the job to become increasingly slower?

    Any clue? or is this a glitch in the software?
Reply
  • Former Member
    Former Member
    something strange.

    I manually duplicated the import job to a job_2. Everything is exactly the same, except for the name_2 and the source folder_2 (which is also local just like first job).

    So now I have the jobs: Import_Converted_Files & Import_Converted_Files_2

    The second job_2 imports like 5-10 times faster than the first job. Exactly the same files, meta data etc.
    How??

    Is M-Files doing something funny with the external source name property? It feels like that there is some form of ever growing registry causing the job to become increasingly slower?

    Any clue? or is this a glitch in the software?
Children
No Data
M-Files
M-Files Support


© 2024 M-Files, All Rights Reserved.