[bisq-network/bisq-markets] Re-implement Markets API service with pre-caching proxy + risq backend (#20)

[dan-da]

@wiz ok, that's good, it seems the opcache is working.  In that case, I'm very curious what kind of traffic numbers you are seeing because the webserver by itself shouldn't start failing until 100's of requests/sec, maybe 1000+, and I really doubt you are seeing that.

Here are my best guesses what is actually the root cause:

1. The bisq app (stats node) is running on the same machine to serve up the json files and is likely hogging too much resources.  If that is the cause, I would recommend to put the bisq app on a separate machine using a shared filesystem so the webserver can access the .json files.  The webserver can then be on a fairly lightweight frontend system.

2. You *might* be seeing some sort of periodic DDOS that is truly overloading webserver.    Are you doing anything to detect and/or mitigate this?

3. some type of apache mis configuration.  (unlikely)

If I were you, the first things I would check are:

1. how many reqs'/sec (or reqs/min) is webserver receiving?
2. Is any API call in particular slower than others?
3. During a time of low usage when CPU is mostly idle, how many reqs/sec can it handle?   (check with ab client, executing locally from server machine, calling each of the APIs).   If you aren't seeing 1000+ reqs/sec eg for depth or trade api's, then something is wrong with installation. example: ab -n 100 -c 2 "https://markets.bisq.network/api/depth?market=xmr_btc"
4. is bisq app using lots or resources (cpu/disk/mem) during times of slowdown?

If you wish to diagnose what the problem actually is now I can assist/advise further with that.  Please open a separate issue in bisq-markets repo.  If you just want to leave it as-is until new system is deployed whenever that is, I'll take my leave from this discussion.

-- 
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/pull/20#issuecomment-552589948
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191111/1ee9f569/attachment.html>