Speeding up uploads...

[tony84]

I have been working on a site, https://shorturl.at/bA1uw

I have used an ai system to build most of the site although some of it is done by me and a developer.

Part of it offers the ability to upload a credit report, which can then pre-populate parts of the system. The problem is that it is very slow - 1-2 minutes which feels painfully slow. When I did it as a standalone system first, it was quite quick - 20-30 seconds maybe. I imagine there is not much I can do as it now needs to work with a much more complex system and a couple of databases but I just thought I would see if anyone had any thoughts?

Cheers

 

[fisicx]

Where do you upload this report? Can’t see it on the site.

Is it the uploading that’s slow or the subsequent analysis?

I suspect it’s the AI bit causing the issue, the code is often very inefficient.

 

[tony84]

When you click on apply, the third part (where you enter adverse) has a section where you can upload a credit report.

It could be that, but when I created the same thing as a standalone product, it was quick. So the same system should be similar?

Im not sure what part of the process it is, you click upload and it just spins for a minute or 2 until it has uploaded and populates the relevant parts. - If you are uploading your own credit report dont worry, I dont see it. It is not saved anywhere, your name, address, personal information does not appear/save anywhere - thats by design.

 

[fisicx]

I’ll have another look but you could add in some console messages to show you (not the applicant) what is happening. A series of checks as it were. You keep refining until you find the bottleneck.

 

[tony84]

It was taking 4 minutes at one point. We have managed to halve it more or less. But struggling to go further.

 

[NelaKo]

Looking at the type of system you’re building, I’d suspect the upload is only a small part of the delay. Once the report hits the server you’re probably doing a few heavier tasks in sequence — extracting the data, running analysis, updating the application fields and maybe calling other services. The standalone version being quicker is a good clue that one of those extra steps is adding the delay. I’d time each stage separately rather than treating it as one upload process, as you’ll probably find one part taking most of that minute or two.

 

[EnterprisePro]

Try with wired Ethernet connection and see what you get.

 

[fisicx]

It was taking 4 minutes at one point. We have managed to halve it more or less. But struggling to go further.

Analyse the process. Put in those markers to see which step is slowing things down. Your console can provide a whole load of data. You can also disable functions as part of the analysis.

 

[tony84]

Cheers. Between this and the AI support, I have a few ideas so will work through them and see what that does.

 

[tony84]

Its still not as quick as the standalone system, but it seems to be much closer to a minute. We seem to have knocked 30-60 seconds off which I think is about as good as we will get without spending a lot of time on it.

I think thats more of a job for the future as we have plenty of other things to be getting on with.

Cheers for the replies, appreciate it.

 

[EnterprisePro]

Also depending on your runtime hosts, uploads could be throttled, if shared. You should probably use a dedicated storage service (S3 or similar) which can permit faster uploads, then have your background tasks queued to pick up and process the uploads, assuming you've made the system async.

 

[tony84]

Also depending on your runtime hosts, uploads could be throttled, if shared. You should probably use a dedicated storage service (S3 or similar) which can permit faster uploads, then have your background tasks queued to pick up and process the uploads, assuming you've made the system async.

Thats on the cards for down the line once things start to take off a little more.