I'm not sure this will be helpful, but after recent outage of the main RPC node(rpc.blurt.world), I think this is something to consider.
Steemit's official RPC node(api.steemit.com) also had some stability issues a while ago. It seems this problem was mitigated by reducing upper limit of account history API.
The official Steemit node's account history upper limit was reduced from 10,000 to 100. I'm not sure this is the main reason, but Steemit's official RPC node has been fairly stable afterwards. I guess this kind of measure could reduce stress on the RPC node significantly.
Below is the Steemit post regarding this update by @ety001:
The official API node will decrease the get_account_history upper limit
Thanks for reading, and I hope this helps in any way.
Thanks a lot for your concern and suggestion, this is indeed a contributing factor to the issue I think, after a quick look I saw it in the source code of Blurt.
@saboin seems to have managed to find a way to split the config to improve the load balancing among highly resource-intensive methods, which have already been optimized by Nexus (equivalent to hivemind), but are extensively used throughout the code in the old frontend and will take some time to be replaced. Now we'll have to wait and see, but I'm confident in what he's achieved.
no problem! let's hope Blurt RPC node gets better!
thanks
no problem!
Dear @joviansummer, your content was selected manually by curators @nalexadre, @ten-years-before to receive a curation from BeBlurt 🎉
Hi, as I see nalexdre already answered on this.
We actually didnt had filters before, so we had to client side filtering, but now its different.
Once we implement the filters, there will be less burden on the RPC.
The filters are currently being tested.
Thanks
that's great. I hope everything will work out smoothly. thanks!