User Pass
Home Sign Up Contact Log In
kaygdanimal
offline
Link
 
I boosted three of my players today and while they are correct on my profile, when I visit My Team Profile (Black Sea Rebels), my RG (Little John) shows up as a Lvl-20 instead of 23, my LT (Porter House) shows up as a Lvl-20 instead of a 23, and my LB (Kaygd Animal) shows up as a Lvl-22 instead of a 23.

Now, on the roster they show up as they should. On the depth chart they show up as they should. However, on the Team's Front Page, they are listed as a Lvl-20. Is there something I need to do so they show up correctly? I understand that they are exactly what they should be and that they will play to their levels in-game but this is just some cosmetic bug where my players aren't showing correct levels on the Team's Front Page.
 
Vagabond
offline
Link
 
The page is most likely cached and since the team profile isnt an "important" page it will most likely be updated during the daily rollover.
As long as the boost is appearing on your homepage everything is find
 
kaygdanimal
offline
Link
 
Originally posted by Vagabond
The page is most likely cached and since the team profile isnt an "important" page it will most likely be updated during the daily rollover.
As long as the boost is appearing on your homepage everything is find


Ah, okay, so it likely is the cache then. I've never understood that stuff, lol. Cache pages are just saved pages right locally, that allows a site to load faster, right?
 
Vagabond
offline
Link
 
right - if you dont have a cache for a place on a website like this EVERY click leads to these actions:

- getting data from the db
- calculation of data gained from the db
- formating the data to a webpage

For 1 click this isnt a problem - but now think of 1000 users doing it PER Secound ( if not more ).

So a very basic cache logic looks like this:

( first request after the daily rollover )
- getting data from the db
- calculation of data gained from the db
- formating the data to a webpage
- saving generated page in memory of server
- sending page to user

next request:
- get page from memory
- sent it to user

Since the data in the memory can be access quite fast you save a lot of time this way AND cpu load - this allows the server to handle more request per secound

A more advanced logic would also try to determine how old the cached page is and if its too old it would be generated again.
Another way could be that the server "knows" that a data of this page has changed and generate the page in the moment of the change of the related data immediatly.
 
RMiller517
offline
Link
 
Thread locked by moderator.
 


You are not logged in. Please log in if you want to post a reply.