Keyword Suggestion

फ्रीमियम
द्वारा Twinword API | अपडेट किया गया 4 дня назад | Text Analysis
लोकप्रियता

9.5 / 10

लेटेंसी

3,892ms

सेवा का स्तर

100%

Health Check

N/A

सभी चर्चाओं पर वापस जाएं

Internal Errors

Rapid account: Xochipelli
xochipelli
6 лет назад

I’ve created this ticket previously, and currently no where to be found. It’s currently showing 3 closed tickets and only displaying 2:
https://www.screencast.com/t/b5eimEKwe4ig

I’m running a project of ~7500 terms and seeing that I’m getting error after error. From what I’ve seen as high as 7/8 calls are resulting in an error.
I’ve added up to 10s delays between calls, and that also hasn’t seemed to help:
https://www.screencast.com/t/eOjw5ya1L

I figured I would let this project run to completion.
I’ve altered my code to identify failed terms and will run those again after this job is done to see how things fair.

Rapid account: Twinword
twinword Commented 6 лет назад

Hi xochipelli,

Thanks for digging through your email. Yes, throttling is necessary for these shared resources on Mashape. You shouldn’t be charged for those errors. If you are, just open a ticket and we can work with Mashape to see what we can do.

Thanks,

Team Twinword

Rapid account: Xochipelli
xochipelli Commented 6 лет назад

Apologies, just found your response to my previous ticket in my emails with some digging.

I do have the project running from a dedicated server.

Yes, I figured delays would help.
So the question becomes the length of delay required?
If I’m scraping G with tools like scrapebox or ubot, I understand the value of proxies and delays.
I’ll jump up my delay to 30s see how that does, and then 60s if necessary and see how those do.

Also, are credits deducted for failed requests?

Thank you for the previous response. Appreciate your support!

चर्चा में शामिल हों - नीचे टिप्पणी जोड़ें:

नई टिप्पणियाँ पोस्ट करने के लिए लॉग इन / साइनअप करें