Forums

Re: Connection Timeout error; Profile Page

• andyson 6,415 Posts

  Tue, May 20 2014 6:47 PM

  Infinito3010:

  Do a file search on your computer for those three files, and look at the size of those files.  Then just use the guideline for HD speed, and you will get the general idea as to why the meter might stutter at an in-opportune time.

  Secondly, if the cache gets too large, then those files will be updated more regularly.

  I had 21,000+ items in my cache using 328MB out of 700MB (~ cache is half full)  the size of the 3 files you mentioned was 31MB.  But I have 344GB free space on my HD so I'm not disk limitied by any means.

  To me the cache and the "indexing" files will be accessed as needed while playing a game.  I do shut down any other browser windows so only the game is changing/accessing the cache.  I don't see how it will be updated more regularly just because its bigger.  During the game it's only serving the game.

  I checked yesterday and the front 9 of STA added 30MB to the cache.  Those files should still be there and if I play STA F9 again I'll have many of the files needed on hand.  I know its also got like the first 5 holes of Pinehurst 2.  I restarted it a couple of times then gave up. LOL   Many of those files were accessed more than once.

  That said, I often wonder when I play the single hole feature under the WGT Community tab above, and I click on Play Again, why there is ANY loading required.  I was just there on the tee!  Those files are in my cache!  You'd think it would be instantaneous?

  And btw, if you're wondering why I have so much crap in my cache.....I use waterfox for everything, not just the game.  Searching for images on Google can load it up pretty good. LOL

  Its working pretty good for me so I'm going to stick to 700MB for now.

   

• Infinito3010 3,689 Posts

  Tue, May 20 2014 8:36 PM

  If it is working well for you, obviously don't change it.

  The assumption you are making is that your ball is landing in the same spot off the tee and on the green for the files to be used more than once. More often than not, you do not hit the same spot .

  Secondly, if you allow for multiple camera angles, then you will hardly ever utilize the same photo twice.

• andyson 6,415 Posts

  Wed, May 21 2014 7:56 AM

  Infinito3010:

  The assumption you are making is that your ball is landing in the same spot off the tee and on the green for the files to be used more than once. More often than not, you do not hit the same spot .

  Secondly, if you allow for multiple camera angles, then you will hardly ever utilize the same photo twice.

  Actually there are at least 4 maybe 5 photos per hole I'd use more than once.  I use the aerial multi-cams to set my aim.  So there's the tee photo, the fairway multi-cam, the approach view, the rear green view, and an aerial view or two.  Call it 4 photos I'd re-use on each hole. At ~280Kb per image and its associated info file that's 1.1Mb per hole.  Or 10Mb per 9 holes. (4x280x9=10,080)

  We can't forget all the Flash files either.  The common swf files used on any course(7.5Mb), the course and hole specific swf files(2.2Mb), and all the avatar files (2.4Mb) will be reused.

  In summary:

  Per 9 hole course reusable in cache: 10Mb Images + 2.2Mb swfs = 12.2Mb

  Files reusable in cache for any course:  7.5 common swfs + 2.4Mb avatar swfs = 9.9Mb

  Total reusable cache files: 22.1Mb

  Allowing for differences between courses it looks to me as if a minimum cache size to play one 9 hole course repeatedly is about 30Mb.

  That's assuming the browser is ONLY used for the game client and nothing else.  That's not my case as I use one browser for everything on the web.

  BUT isn't this whole discussion moot if the Background Loading option is turned off?  (assuming that feature works as stated of course)  We're not accessing the disk cache or the WGT server during a swing so how can it cause a stutter?

   

   

• Infinito3010 3,689 Posts

  Wed, May 21 2014 1:53 PM

  The data gets stored in those three files. It tells the browser, where the file is stored, and its name. The garbage collection routines of the browser flushes the data to disk. Including, the information stored in those files.  Thus, meter stutter, is not predictable. 

  You would think with the background load option turned off, that this would be an issue and it shouldn't be.

  You must be one of the lucky ones, because at most, those HD photos only got used twice over a period of 3 weeks for me.  The files, are jpg, and they are relatively small.

  Happy hitting, and may the meter be with you.