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

M-Files as a storage for frequent big documents

Hi there,

I was approached today with a requirement to save big technical reports containing picture snippets and summaries. These reports are usually between 250-500MB each and they are in PDF format.
Another point is that these reports could easily be produce 1-10 times per month.
So if I calculate a middle case 5 documents of 300 MB per month I coming to 60 documents with size 17 GB.
I have did some load test with 200-250MB files over REST based API and it was not particularly fast (obviously due to size of a document). I am currently not aware about complexity of metadata for that specific document type. This can of course influence uploading speed as well.
I am not aware on any document size limit in M-Files but wondering if M-Files is a proper solution for such a use case.
I am also worried because Vault will grow to be quite big and this could influence other document types used in a system (planned 50-100 document types).

What are your experiences with big frequent documents? I would appreciate your experiences.

Dejan
Parents
  • Hi Karl,
    Those are great points. Thank you very much.

    We will be on-premise in intranet so hope it would work well.
    For preview, as you mentioned document needs to get saved before previewing. What user expects is often: they change value on metadata card and want to preview it again and see the old value. It is hard to explain people that they need to checkout document to see new metadata there. That is the problem.
    That what you mentioned with embedded metadata is interesting but if it is not working well with desktop client, again is not very useful. I always thought if we automate pdf converting M-Files would pick up the latest metadata values but it does not work like that unfortunately.

    Many thanks for insights. That really helps.

    Dejan
Reply
  • Hi Karl,
    Those are great points. Thank you very much.

    We will be on-premise in intranet so hope it would work well.
    For preview, as you mentioned document needs to get saved before previewing. What user expects is often: they change value on metadata card and want to preview it again and see the old value. It is hard to explain people that they need to checkout document to see new metadata there. That is the problem.
    That what you mentioned with embedded metadata is interesting but if it is not working well with desktop client, again is not very useful. I always thought if we automate pdf converting M-Files would pick up the latest metadata values but it does not work like that unfortunately.

    Many thanks for insights. That really helps.

    Dejan
Children
No Data