Zorg Empire

Greetings everyone,

We have heard some concerns about X-TREME universe lag performance.

We do want to reassure everyone that we are actively monitoring the situation. We have already updated the ranking script to the one Massacre is using and which will considerably fight off the lag created at xx:10 times.

If you experience lag, please post here, as we are actively monitoring and tweaking the system, as needed.

It is important to know how to DETECT lag:
The only SAFE way is to go to your galaxy page. At the top of it, it reads:
Page generated in 0.049 seconds
This indicates the time needed by the server to generate the page you are viewing.

So, the next time you experience lag while playing, please go at your galaxy page and start going to one system after another.
Check to see how the page generation times flow while you scan a galaxy. Acceptable timings should be up to 0.200 for systems full of planets.
Even ocassional times up to 2 seconds.These indicate the so called spikes of lag. If the spikes are many, we would still like to know.

What to do:
-In case you experience constant lag spanning from 0.5 seconds and higher (as mentioned in galaxy page) please post here.

What to post:
-Game time it happened
-How much time on avg each system took to load, minimum and highest values too (please avoid exaggerations from what you read in the galaxy page)

We have already issued a tweak and we want to see whether or not this will be enough.

Also, for your own convenience, here is how time to show a page is breaked down into pieces:

Total time = Page generation by Server + Page delivery by Client
Average server page generation times across all pages is 0.05 seconds.
If your total time (there are browser addons that calculate it) is let's say 3 seconds then the 2.95 seconds are needed by your browser and the 0.05 seconds by our server.

Our server affects page generation.
Connection speed affects page delivery times. Both the connection speed of the game and yours play a role. Connection problems of Zorg Empire are extremely rare and you can track these from our monitor page: http://www.zorgempire.net/status/
Your system affects page delivery time. (CPU and RAM mostly)
Your browser affects page delivery time. (Chrome seems to be the fastest for pcs, right now)
Your operating system affects page delivery time.

Installed Google Chrome after reading Zorgs post. It was pre-installed on my tablet so I thought I'd try it on my PC. Have been using Firefox and lately there's been issues where it would stop responding. I couldn't be happier with Chrome. The page response is incredibly fast.

Administrator wrote:(Chrome seems to be the fastest for pcs, right now)

You have got to be kidding. A game that is only optimal in a single browser??? That is not good. I refuse to use the Google Chrome web browser because of conflicts with my PC. If that is the best you can do, then you might want to get some web developers that know how to program in IE and Firefox. Those are the most common browser being used by the entire world.

Torgard wrote:

Administrator wrote:(Chrome seems to be the fastest for pcs, right now)

You have got to be kidding. A game that is only optimal in a single browser??? That is not good. I refuse to use the Google Chrome web browser because of conflicts with my PC. If that is the best you can do, then you might want to get some web developers that know how to program in IE and Firefox. Those are the most common browser being used by the entire world.

Have you actually read the whole post ? Even if you haven't where exactly in the bracket it says that the game is only optimal for a single web browser?

We are optimal for ANY web browser. Google Chrome is FASTER for ANY webpage (not just for us) mainly because of the way it uses RAM. If you got a slow pc, then switching to Google chrome will help your internet browsing speed generally.

ZORTON wrote:Installed Google Chrome after reading Zorgs post. It was pre-installed on my tablet so I thought I'd try it on my PC. Have been using Firefox and lately there's been issues where it would stop responding. I couldn't be happier with Chrome. The page response is incredibly fast.

Perhaps it may also be the result of our work on the server as we have considerably improved server performance in the last 2 days.

you might ask for help from player base who actually know a bit of web programming and have clear understanding on how to carry out the browser dependency issues resolved so that all browsers may work similarly. that is saying if you are not capable of doing it!! ~~~ yes a definite pun intended in it.

also if i can say there are ppl who can resolve these issues from player base then from developers of this game i expect better throughput so they take more care and time to resolve the issues. unable to do so kinda means you guys are being just lazy buggers in front of the game display code part.... !!! ~~~ yes another back to back pun intended

so dont be inadequate and dont be lazy. excuses are only pretty as long as they are to have booze.

@Zorg

My problem was with Firefox in general, not a lag in Xtreme. The browser itself would stop responding, regardless of the site. Firefox is a RAM pig and the more tabs you have open, the worse it gets.

am using goggle chrome sometimes it takes 2 min to change to galaxy after a clicked on galaxy
or a click on overview and it starts loading and nothing happens.then a must quit extreme and relogin again.

ZORTON wrote:@Zorg

My problem was with Firefox in general, not a lag in Xtreme. The browser itself would stop responding, regardless of the site. Firefox is a RAM pig and the more tabs you have open, the worse it gets.

Yeah, I had the same problem generally till I switched browsers. I have a friend that still uses FF 2.0 and refuses to upgrade it

Although to be fair, FF supports a lot of goodies like CSS3 and also "fixes" developer mistakes while Chrome does not. Also, FF will run fine in a strong PC.

Uhh...

Edit: Now up to 116% but still offline.

For future reference, 116% means that we are working on it. It is fixed now.