scalability of the plugin

[nanu-c]

First 1000 thanks for this ticker its simple and great :)

In the current version on the wp-plugin repository the ticker is broken, because the date query is wrong

'date_query'     => array(
   'after' => date( 'c', $last_poll ),
)

'c', $last_poll results in 2020-04-26T21:05:24+00:00 but wordpress is expecting something like 2020-04-26 20:56:22.
Solution is

'date_query'     => array(
   'after' => date( 'Y-m-d H:i:s', $last_poll ),
),

Then i looked in your code here and saw, that you solved it already.

---

So my main concern is now, if you have 20.000 simultaneous visitors who are making a ajax every 20 seconds and every call results in a db poll leads to a problem ;)

[stklcode]

Thanks for your feedback.

You are right, the first part has been solved with upcoming v1.1.

Assuming you’re not displaying thousands of ticks, the actual DB load for a single query is rather low. However a good point.
I will try to utilize WP caching mechanisms to reduce DB load in such scenarios.

[stklcode]

So my main concern is now, if you have 20.000 simultaneous visitors who are making a ajax every 20 seconds and every call results in a db poll leads to a problem ;)

With the next version 1.2 the AJAX calls will target the REST API instead of the AJAX endpoint and will use the modification timestamp of the latest tick received. (see #15)

This will have two posititive impacts here:

1. all visitors will use the same "lastPoll" value of no new tick has been published in between
2. doing so the API requests are equal and can be served from cache