highly dobutful that the decrypter takes that long when everything goes right. As in time could increase/vary slightly if additional http request caused by connection timeout issues are required, or password prompting or album forwarding takes place. Also if you add links that are not in the following format, imgsrc.ru/username/a\d+.html, more page requests take place in order to make sure it's decrypting on page one of given album. The slow part of the original decrypter was processing of each of the img urls imgsrc.ru/username/(\d+).html (notice no a) to get the direct http url of the image. This is now done in the dedicated hoster plugin. Since my previous change to this plugin (a month or so ago) I placed in a time to decrypt output in the log. Though now displays in seconds and not minutes as the decrypter works fast!
the link you provided in this thread for example
62|imgsrc.ru 29/05/13 12:44:46 PM - INFO [ jd.plugins.decrypter.ImgSrcRu(decryptIt) ] -> Time to decrypt : 1 seconds. Returning 43 DownloadLinks for
a few tests of my own
84|imgsrc.ru 29/05/13 1:33:57 PM - INFO [ jd.plugins.decrypter.ImgSrcRu(decryptIt) ] -> Time to decrypt : 2 seconds. Returning 68 DownloadLinks for
86|imgsrc.ru 29/05/13 1:34:48 PM - INFO [ jd.plugins.decrypter.ImgSrcRu(decryptIt) ] -> Time to decrypt : 1 seconds. Returning 43 DownloadLinks for
114|imgsrc.ru 29/05/13 1:40:30 PM - INFO [ jd.plugins.decrypter.ImgSrcRu(decryptIt) ] -> Time to decrypt : 19 seconds. Returning 705 DownloadLinks for
151|imgsrc.ru 29/05/13 1:44:45 PM - INFO [ jd.plugins.decrypter.ImgSrcRu(decryptIt) ] -> Time to decrypt : 21 seconds. Returning 898 DownloadLinks for
considering my ping to imgsrc is half a second, performance wise that's a great outcome.
Last edited by raztoki; 29.05.2013 at 08:04.
|