Skip to main content

Test Operation

Testing your cache

Now you’ve configured your dns, started that stack and are ready to test things are operating. Here’s some very basic diagnostics and tests we would suggest to run to see if things are working.

  1. Check your dns is being intercepted
  • Run a few queries using command prompt to check that your dns is pointing at your cache, the following should all result in your cache ip if everything is working
ipconfig /flushdns
nslookup steam.cache.lancache.net
nslookup lancache.steamcontent.com
  1. Download a game through steam
  • If everything is working you should find the first time you download a game speeds which are equivalent to your internet speed. You may find that initial downloads through the cache are slightly slower, but thats ok.

    Why do we cache

    We cache traffic in order to provide benefit to many users in a large environment. LanCache is optimised for hundreds to thousands of gamers downloading at once not one or two users on a small scale. The emphasis is always on superior cached performance over uncached.

  1. Uninstall the first game and download again
  • This time you should find your game downloads much faster (depending on your limiting factor: Server Disk, Client Disk, Network, see hardware.
  1. Try a few other cdns

  2. Precache some of the more popular games you might expect to happen at your event

  • Although precaching isn’t necessary, it certainly helps the initial demand on a cache when everyone turns up at the same time.
  1. Get your friends round and enjoy the entire lan being able to download a game for only 1x external traffic.