It interferes a lot, this should not be done in general. You need an event system (the mechanism is this, but the architecture for client / server is different).
Using the Hollywood Principle, the client registers itself on the server telling what context it is and what it wants to be notified, then the server sends something to the client when a change relevant to that subscriber happened.
The update system is only interesting when almost all requests will bring new relevant information.
Today we often use reactive programming that raises the event system to another level. There's plenty of ready to do push notification . For example, in C # you usually use ASP.NET SignalR . But you have other options .
For some, such as for PHP (I do not know if it's good) or ReactPHP .
There are API services that do this, but it does not seem like what you want.
But the basic idea is to use Web Sockets . The technique is often long polling . Also look for asynchronous notification.
Dealing with Web Sockets Direct can be pretty annoying and it's easy to do wrong, I would not waste time, unless I wanted to go deep into it. Choose a more ready solution.
This is how this site, Facebook, and many others work.