Atomic counters and concurrent request limit

General
1

Hi Backendless Team,
I run into situation where when retrieving more than 100 atomic counters I receive error message of concurrent request limit of 100.

My App logic is that current month leaderboard participants and their points are stored as atomic counters.
In Cloud code I have method that retrieves all participants, and just today started to think, what will happen if I have more than 100 counters to retrieve, since there is no page size and offset, as to Load table objects block…
So did create test for that, and it ended up with error message about concurrent request limit of 100.

Is this expected behavior with atomic counters, or there is way to retrieve more than 100 atomic counters at once?

2

Hello, @Uldis_Borkus.

Can you please answer to a few questions.

  1. Which method do you use to get counters?
  2. Can you show some example of your usage/minimal reproduce forwards?

Regards, Nikita.

3

Hi @Nikita_Fedorishchev

  1. This was the method:

    image
    image910×205 32.8 KB

  2. Recreated example, but seems that I no longer get the concurrent request limit, but now it is one I control, with tier threshold. So no more issues there. At least for now.

And now it is clear that my logic with atomic counters would get costly in long run, will redo to use db instead.

Resolving this one.

1 Like