Timing issue with upload and overwrite:false
I have a question about image asset uploading when overwrite is set to false. I'm testing locally with 23 images, and using overwrite:false in my upload calls. Whenever my code runs, it takes about 20 seconds to process. Given that the images already exist, shouldn't it be going a lot faster? I've got a good connection so that shouldn't be it. You can see my source here;
https://github.com/cfjedimaster/eleventy-demos/tree/master/cloudinary1
Specifically src/_data/photos.js.
Are these timings expected?
-
Hi Raymond,
I would suggest adding a timer for each upload in the code and seeing where it is consuming most of the time.
Maybe there is an image that is heavy in size.I could check your logs if I had your Cloud name.
Could you open a ticket by filling out this form:
https://support.cloudinary.com/hc/en-us/requests/newRegards,
Wissam
0 -
But if I have overwrite to false, why would it upload?
0 -
Hi Raymond,
When the overwrite parameter is set to false, a response is returned immediately if an asset with the same Public ID was found and the upload response will contain: "existing": "True". The second upload is faster based on the tests done for the traces below.
In case you are experiencing some delay, kindly help to raise a support ticket providing the responses (or log traces) from your application so we could further investigate it.
First upload response:
Second upload response:
0 -
As requested, I filed the issue here, https://support.cloudinary.com/hc/en-us/requests/204562. To be clear, I know how overwrite is supposed to work, it just doesn't seem to be working for me. Ie, even though overwrite is false, it still takes 30ish seconds for the code to run, despite the images already being uploaded.
0
Post is closed for comments.
Comments
4 comments