2 months ago
I am running a n8n instance on the server. I am creating videos on the server in the work flow. I am trying to use the read files from disk node to have my newly created mp4 files read as a binary file to upload to my google drive account. But this node is being super slow.
The node takes about 30 seconds for it to read a 11 MB mp4 file, about 7 minutes to read a 50 MB mp4 file and I stopped it after a half an hour of it trying to read a 100 MB mp4 file. I am wondering if it is my instance of n8n, my workflow, where I am storing the mp4 file, or if there are limitations on the storage to read files for why it is struggling.
I am on the pro plan and I have no other instances of my workflow running. I am still manually testing my workflows so there is nothing else running while this node is trying to read the file. Looking to see if someone has an idea I could try out to get the files read faster so I can move them to my google drive.
All the files I download on the server for the video creation and all the video itself are considered temporary files until the final mp4 file gets uploaded to google drive then all the files get deleted after every workflow.
1 Replies
2 months ago
This read/write issues you are experiencing are unrelated to the Railway platform. You might want to take a look at the n8n template with workers, which includes an end-to-end working setup of n8n, including databases with persistent Volumes.
Status changed to Awaiting User Response railway[bot] • 2 months ago