![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
(no subject)
Apr. 8th, 2011 04:53 amI've seen people wondering why imports are taking so @)#$(*& long. This might help shed some light:
( a very small excerpt from our job logs )
1) LJ is still under wicked load due to the DDoS they're experiencing. This can mean the site timing out when we try to contact them for the data.
2) Every time LJ is inaccessable when the importer tries to hit it, the job goes on pause to retry again in a few seconds. It retries up to five times before giving up.
3) There are lots and lots and lots of people trying to import right now. (This means that imports from sites other than LJ will be slow too, because they enter the queue behind all the LJ import jobs.)
If I had to guess, I'd say the existing import queue as it stands right this very minute would take at least 24 hours to clear, because of a combination of the three above items. Please, please, please be patient!
( a very small excerpt from our job logs )
1) LJ is still under wicked load due to the DDoS they're experiencing. This can mean the site timing out when we try to contact them for the data.
2) Every time LJ is inaccessable when the importer tries to hit it, the job goes on pause to retry again in a few seconds. It retries up to five times before giving up.
3) There are lots and lots and lots of people trying to import right now. (This means that imports from sites other than LJ will be slow too, because they enter the queue behind all the LJ import jobs.)
If I had to guess, I'd say the existing import queue as it stands right this very minute would take at least 24 hours to clear, because of a combination of the three above items. Please, please, please be patient!
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}