M
M
maksustoff2017-04-06 06:44:46
In contact with
maksustoff, 2017-04-06 06:44:46

"Too many requests per second." Is there anything I can do?

An application that receives two user IDs in a social network and analyzes the possibility of communication between them through 6 nodes ("six handshakes"). A "graph" type structure is built and for each vertex (key - ID) we get a list of friends and so on, through the stack. The problem is the "3 requests per second" limit, we get only three processing nodes, and even communication through two nodes will take a decent amount of time, for six "do not wait". Is there any way to deal with this problem?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
D
d-stream, 2017-04-06
@d-stream

Well, here "on the forehead" you can't fight the given. If the estimated number of requests is 300 pcs, then taking into account the limit - 100 sec ...
Then just look - this limit applies to one ip or one account, if "on one ip" - well, then we are smeared across several proxies, if "to account" - then we make several accounts.

U
Uno, 2017-04-08
@Noizefan

A good option is to use method.execute.
Or I just discovered such a feature - by creating a VKontakte community, you can generate a huge amount of access tokens. If the api methods you use allow - I recommend this option. 50 tokens is 150 requests per second, which is twice as much as with three executes/sec.

T
Tsiren Naimanov, 2017-04-06
@ImmortalCAT

before each request, use for example this is a rough solution to the problem, look at the vkapi sources

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question