Read the statement by Michael Teeuw here.
Finding module with high external traffic
-
The modules I use all rely on local data sources. I run my instance in server-only mode. Still, I see unexpected traffic to a google-hosted IP address. How can I find the culprit (and stop it)?
-
@mmmmh Which modules are you using?
-
@Sean if you dnslookup that ip address, does it have a name associated?
-
@Sean I think I found the “culprit”, it may be the Spotify module’s polling. I just increased the interval and will see if the traffic decreases.
-
@sdetweil the IP resolves to a generic Google host, currently 53.224.186.35.bc.googleusercontent.com - I think it is used by Spotify.
-
@mmmmh Yes, it retrieves requests per 1~2 seconds. Unfortunately Spotify Web API doesn’t support push mechanism to get status updated. So it needs pooling. I recommend 2000 ms or more frequency to update current playback if you don’t care.
-
@Sean I think I read somewhere that callback addresses could be provided (perhaps I misread this). If I have a DynDNS-backed FQD host and forwarded port I can provide, would this stop the polling requirement?
-
@mmmmh I don’t think so. To update current playback info (The playing status, playing time,…) on real time, This module has to call Spotify Web APIs frequently.
-
@Sean I checked again, you are right, polling is the only option. Thanks for your cool module!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login