Import really slow or fails.
Permalink Browser Info Environment
Hello.
We have a problem with our hosting running somewhat slow at the moment, but it highlighted a problem with this plugin, compounding the problem on the server. Another Concrete5 developer looked into the problem for us and came back with the following.
The all-in ajax bump-along appears to be flawed. I think it is supposed to be doing a sequence of requests: check - delete - run - status. What it is actually doing is a continuous loop of check -check -check ..... until it gets a response to a check, then does delete - run - status, before the endless cascade of check -check -check ....... again.
I didn't notice this on my dev system at first because it is fast and there is usually a response from the server within the first few checks, so it doesn't get overloaded.
On our live site, because it is slow, it builds up a backlog of a few hundred pending 'check' actions before it gets an answer from the first one. It then tries to do the delete - run - status part, but that is only occasionally successful because the server is still saturated with the endless check - check - check..... then at some point the server concludes it is completely over-saturated and 'goes away', so a bunch of requests fail.
However, the underlying problem is the all-in javascript saturating the server with repeated 'check' actions without waiting for a response from the first such action.
We have a problem with our hosting running somewhat slow at the moment, but it highlighted a problem with this plugin, compounding the problem on the server. Another Concrete5 developer looked into the problem for us and came back with the following.
The all-in ajax bump-along appears to be flawed. I think it is supposed to be doing a sequence of requests: check - delete - run - status. What it is actually doing is a continuous loop of check -check -check ..... until it gets a response to a check, then does delete - run - status, before the endless cascade of check -check -check ....... again.
I didn't notice this on my dev system at first because it is fast and there is usually a response from the server within the first few checks, so it doesn't get overloaded.
On our live site, because it is slow, it builds up a backlog of a few hundred pending 'check' actions before it gets an answer from the first one. It then tries to do the delete - run - status part, but that is only occasionally successful because the server is still saturated with the endless check - check - check..... then at some point the server concludes it is completely over-saturated and 'goes away', so a bunch of requests fail.
However, the underlying problem is the all-in javascript saturating the server with repeated 'check' actions without waiting for a response from the first such action.
| Type: | Pre-Sale |
|---|---|
| Status: | Archived |
Hello. Thanks for getting back to me. Have a good trip.
Hello again.
Hope you had a good trip.
Have you managed to have a look at the problem yet?
Thanks,
Russell.
Hope you had a good trip.
Have you managed to have a look at the problem yet?
Thanks,
Russell.
Just wondering if you have managed to have a look at this yet?
Sorry for the delay in response. I'll be traveling over the next few days so I'll have limited time to look at the two issues you posted.
However, if you are okay with it, I'll dedicate a significant portion of time on next Monday 11/27.