[bisq-network/bisq-markets] API connection timeout (#1)

[dan-da]

>  I find however that going from 180 req/min to 15 req/min is a bit rude.

Agreed it is not ideal.  Again though, it was put in place to mitigate a ddos attack that was killing the site.  Bisq is quite limited on server resources so we have to make do within constraints.

This is the first comments I've seen about it since the limit was lowered.

At this point with the caching in place and current traffic I feel it could safely be raised to 60 reqs in 120 secs ( 2 secs per req ) and still withstand a ddos, if not too huge.

That said, hopefully traffic will continue increasing, so our present server resources will scale approx twice as far if we continue with the 4 secs.  So I'm leaning towards keeping status quo for now.

Either way, I think the most important thing is to document the limit.

anyone want to weigh in on this before I make any change?   any use cases that are seriously adversely impacted by a 4 sec limit?    or has anyone heard complaints of browser sessions being banned? 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq-markets/issues/1#issuecomment-422624861
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180918/cb0c75f2/attachment.html>