I noticed that many RSS "readers" receive the news almost immediately after publication on the site:

  • Do they so often turn to the resource for an update? (I myself use RSS Feed Reader in Chrome). How often, on average, appeals occur?

  • How can I reduce the frequency of requests on the server side? Or use other optimization methods?

  • Can a large number of subscribers "load" the server?

    1 answer 1

    How can I reduce the frequency of requests on the server side?

    This is the task of the reader. Because you do not need to immediately climb everything pumped out, but you must use If-Modified-Since (some do first HEAD and watch Last-Modified). Accordingly, the server must correctly give Last-Modified.

    • Well, if the content is issued dynamically, and when you query into the database, you still have to climb to see if it has been updated? Is it possible to set the time that is optimal for the update? - michael
    • one
      First, the client cannot know in any way how often the RSS is updated (as an option, give the special value item, for example, but this is a special and not universal case). Secondly, in over 9000 cases, static can be given instead of dynamics. And thirdly, Last-Modified in RSS is present by definition (the most recent pubDate), and this business can be stored separately, and in any case, given quickly, even in the case of dynamics. - user6550