Resolved Import: Slowly, error message and more

Hi,

Too dense, too complicated. It needs to be idiot-proof and with images, I think…

Writing perfect documentation is a challenge. What might be idiot-proof for one, can still be complicated for another. One person asks for images, the next asks for videos, we are trying it all. Writing documentation is not that easy but we try. If not, we are always here to help.

That is the reason we also supply out-of-the-box templates that can be used as a starting point. By the sounds of it, you have not used those.

I’ll try to figure it out on my own.

There is no need to do it alone, we are happy to help.

The server has huge resources

Sure but the server may not be the issue at all. If you are pulling remote images, your server is sitting idle waiting for a response from the other end. It is just one of many reasons an import can be slow.

Not even the CSV downloaded with your component could be re-uploaded.

That is possible if you created your own export template containing fields only used for export.

Our impossible documentation is just has hard as giving you valuable feedback without any information. That is why we ask for a number of things on the RO CSVI category page. That will give us some insight into what you are doing.

The website is frozen during this process, and the import is extremely slow—about 3 seconds per record.

You mean to say the whole website or just the import page?

This message appears during the import: "The last server response has not been received in a timely fashion. The server may still be busy or stopped the process. You can wait a little longer to see if the server will sent a response or cancel the process".

We show this message based on a guesstimation, we check the max_execution_time and count how long there has been no response. If the no response is longer than the max_execution_time the message will show up. As a web application we have no access to system resources to see what is really happening.

Is this normal? The Excel file has approximately 5,500 rows and 5 columns.

Uh no, I would not expect 3 seconds per record, not even close actually. However if you have 1 record with 20 images pulling from a remote server it suddenly is not so strange anymore.

Let me know what you are trying to import and I will have a look.

Honestly, I have no idea how your component works… It took me four hours to get it to work after getting lost in your documentation. Too dense, too complicated. It needs to be idiot-proof and with images, I think…

Now it works, somehow, and I didn’t really do much. It’s a mystery. But it’s extremely non-intuitive.

Thanks for the response, but it has nothing to do with what’s actually happening.

The server has huge resources—I can import and export the entire database in just a few seconds. I’m only trying to manage a small part of it with your component, but it’s physically exhausting.

Too complicated to use. That’s it. Close the topic, it’s fine. I’ll try to figure it out on my own.

PS: I can’t import CSV at all. (5 hours...ups) Not even the CSV downloaded with your component could be re-uploaded. It is what it is.

Have a nice day.

Hello,

Is this normal? The Excel file has approximately 5,500 rows and 5 columns.

This happens when server limits are reached while processing records in given time limit. Read Manage Timeouts document to know how to handle this error. You can reduce the number of records processed from Limit tab in CSVI import template. By default Lines per import is set to 1000. Reduce this to 500 or to any lesser number and run the import. See how it goes.