| Pages: 1 2 3 4 [5] :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 3 post(s) |
Wolke 7
   |
Posted - 2010.01.28 12:45:00 -
[121]
 Originally by: Miklas Laces
Originally by: CCP Tanis
I'll use this opportunity to bring up that though this particular test doesn't require too many people (only 100+), we will certainly be running more tests to isolate the causes of the current lag on TQ; however, those will require far higher numbers of pilots in order to replicate the behavior that we're seeing on TQ.
We have had issues in the past trying to get more than 200 pilots who actually show up, so we will be trying to find new ways to get players into Sisi for these bigger tests. Details are still being worked out, but we're still feverishly working away at this issue in the meantime. We'll be releasing more info about the larger scale testing soon™.
Why do you need players help, cant you run 100 eve clients in your damn software company ?
My thoughts, emulating clients should be a basic task.
Also, if there is something wrong after a major patch why do it all ass backwards? Compare the two builds, debug changes. Not forebode through "logs". But obviously that would have to happen before implementation.
|
kyrieee
Psykotic Meat
Wildly Inappropriate.
|
Posted - 2010.01.28 16:32:00 -
[122]
Originally by: Caladain Barton
Originally by: CCP Tanis
We'd like to extend our gratitude to all those who participated in today's test!
We were able get a very good reproduction of the issue on Sisi and gathered some very good data about the lag issues; which we will be spending the next days pouring over to try and isolate the cause of the problem.
Rest assured we've got our best people on this issue and we will keep at it until we've solved it.
If you want to replicate the large fleet battles, You know where to find me and Others, and you know what has to be done. The testing done may have shown where the laggy code is..but you didn't recreate the issue. No one black screened and failed to load. Doesn't mean you didn't find *a* problem, but you can't be happy you didn't replicate it, eh?
If you want a full, NC CTA, you're going to have to freeze Sov for a couple hours, have the patch ready to go so we can spam our members to install it, pick a weekend, and pick a time. We'll pull a full CTA..everything and the kitchen sink and show you exactly the issues currently existing with whatever manner of logger running, and without shooting each other or goofing off, by recreating the situations exactly. If CCP does this, i'd invite Atlas and friends, and Tri and Friends to come as well..do it pro, do it right, and after they've collected their data, we can go at each other.
And FFS...we'll open a TS server and get everyone on it with a 0.0 FC team...TS/Vent=WIN. Eve Voice=Fail.
QFT
|
J'J'J'Jita
|
Posted - 2010.01.28 17:08:00 -
[123]
Originally by: CCP Tanis
I'll use this opportunity to bring up that though this particular test doesn't require too many people (only 100+), we will certainly be running more tests to isolate the causes of the current lag on TQ; however, those will require far higher numbers of pilots in order to replicate the behavior that we're seeing on TQ.
We have had issues in the past trying to get more than 200 pilots who actually show up, so we will be trying to find new ways to get players into Sisi for these bigger tests. Details are still being worked out, but we're still feverishly working away at this issue in the meantime. We'll be releasing more info about the larger scale testing soonÖ.
For larger scale testing, how about sending emails to Eve players with the time/date? I'm sure only a small percent of players actually reads random testing announcements or the forums. Everyone reads their email.
Holding it at a time not in the middle of US TZ workdays would be nice too.
|
Caladain Barton
Navy of Xoc
Wildly Inappropriate.
|
Posted - 2010.01.29 01:10:00 -
[124]
Seeing as how this wasn't fixed with this patch that supposedly fixed it, my offer still stands.
|
Ga'len
Minmatar Ship Construction Services
Ushra'Khan
|
Posted - 2010.01.29 01:46:00 -
[125]
Well, it happened, we have a major fight in D-GTMI tis evening on TQ.
We peaked in system at 1695 in local. Yup, almost 1700 and the node DID NOT CRASH!
Here is an idea of the carnage:
http://www.a-kills.com/?a=kill_related&kll_id=353731
We encountered lag of course and at times, grid loading would take up to 10 minutes, module response times varied greatly between instant as it should be to 20+ minutes. The module lag was not consistent, it seemed to hit random people at random times. Fleet and local chat were also lagging when we were close to 1700 with chat entries taking up to 5 minutes to present.
Almost 1700 in system is a HUGE accomplishment. I don't know what the back end optimizations that were done with Dominion 1.1.1, but I know this:
1695 in system, over 1200 on grid and the node DID NOT CRASH.
I know I have been very critical of CCP and they work they seemed to be taking forever to complete. From this one engagement, I can see that they have actually done something to help resolve the problems.
It's a step in the right direction, keep up the good work CCP!
|
Caladain Barton
Navy of Xoc
Wildly Inappropriate.
|
Posted - 2010.01.29 02:15:00 -
[126]
Originally by: Ga'len
Well, it happened, we have a major fight in D-GTMI tis evening on TQ.
We peaked in system at 1695 in local. Yup, almost 1700 and the node DID NOT CRASH!
Here is an idea of the carnage:
http://www.a-kills.com/?a=kill_related&kll_id=353731
We encountered lag of course and at times, grid loading would take up to 10 minutes, module response times varied greatly between instant as it should be to 20+ minutes. The module lag was not consistent, it seemed to hit random people at random times. Fleet and local chat were also lagging when we were close to 1700 with chat entries taking up to 5 minutes to present.
Almost 1700 in system is a HUGE accomplishment. I don't know what the back end optimizations that were done with Dominion 1.1.1, but I know this:
1695 in system, over 1200 on grid and the node DID NOT CRASH.
I know I have been very critical of CCP and they work they seemed to be taking forever to complete. From this one engagement, I can see that they have actually done something to help resolve the problems.
It's a step in the right direction, keep up the good work CCP!
You mean the node didn't suck for you...CVA got stuck on the black screen.
But yes, the node didn't die. So..progress?
|
Ga'len
Minmatar Ship Construction Services
Ushra'Khan
|
Posted - 2010.01.29 03:53:00 -
[127]
Edited by: Ga''len on 29/01/2010 03:53:27
Originally by: Caladain Barton
You mean the node didn't suck for you...CVA got stuck on the black screen.
But yes, the node didn't die. So..progress?
This is a discussion on lag, I will not engage in a COAD discussion here.
The system remained up and running, the fight is over.
As for CVA, many of them were actively fighting as far as I could see. I was in one of the dreads on the -A- side and they were both locking us up and firing as often as we were locking and firing on them.
I do know that we had a large number of people who could not get logged in or jumped into system around the time the local population reached 1600.
Someone mentioned that systems cap at 1700. I don't know if that is the case, but if it is, it may explain the complaints of not being able to log in that we were hearing and what you may have heard from CVA.
If you want to hear more about the fight, you should head over to COAD for the details.
|
J'J'J'Jita
|
Posted - 2010.01.29 07:36:00 -
[128]
He wasn't making it a political discussion. He was trying to provide information: some/many people warping _in_ to the system were stuck on a black screen and never loaded in time to fight. That's relevant to troubleshooting the problem, and frankly, sounds a lot like the reports from the PL fight in early January. So maybe 1.1.1 didn't fix that much after all.
|
Gilgadroll
Construction Cabal
Ishuk-Raata Enforcement Directive
|
Posted - 2010.01.29 14:07:00 -
[129]
Did all the usual large scale fleet battle preparations. Joined the battle in D-G right after the unexpected downtime. Warped with 200 other fleet members to begin the battle. The grid partially loaded after 20 minutes. Guns cycled every 3 minutes or so on manual. When the reds arrived they never appeared in a manner where I could target but yet I was being targeted by them.
1 hour later I woke up in my clone apparently destroyed by a red ghost pod which was the only thing I could see outside of deployables on overview or visual. I think I managed to spew out 3-4 rounds of ammo and 5-6 missiles on a large mobile warp disruptor. I was able to view my wreck on a screenie taken by a victorious -A- member 
|
Numerenor
|
Posted - 2010.01.29 18:41:00 -
[130]
I am also considering canceling my account, along with 90 other people that i have been in contact with unless our very very expensive losses, are replaced and the game fixed as having your capitol fleet desotryed while your not even logged in , or waiting 3 hours for screen to load, totaly takes the Pi##
|
|
|
Dr Karsun
Gallente
HUSARIA
Curatores Veritatis Alliance
|
Posted - 2010.01.29 19:00:00 -
[131]
Originally by: Numerenor
I am also considering canceling my account, along with 90 other people that i have been in contact with unless our very very expensive losses, are replaced and the game fixed as having your capitol fleet desotryed while your not even logged in , or waiting 3 hours for screen to load, totaly takes the Pi##
I'm pretty sure your losses won't be replaced because the server log will say that you never logged off or dced... Or maybe it'll even say you logged back in later? Who knows?
And seriously, didn't even get to fight in the d-g fight... Didn't manage to undock from station - after 15 minutes of waiting for undock the server booted me and didn't allow to log back in for another 20 minutes when I gave up. Today I logged and saw that I never even left the station.
But seriously... CCP... over 50 capital deaths just because one fleet completely lagged out and 0 losses on enemy side doesn't really look nice. |
Ravenariel
Caldari
BlazingAngels
|
Posted - 2010.01.29 21:38:00 -
[132]
Edited by: Ravenariel on 29/01/2010 21:41:02
My first 00 large fleet battle was quite an experience. Got to ride a titan jump bridge which was cool... not making the crossing was a bummer...win or lose I wished I could have atleast seen it. But while were were desynced my group passed time talking to various pilots in and out of the grid to compare notes to see what was actually happening. Here is a summary.
Just after 2300 we were ordered to jump and local was reported i think just over 1400, there were about 50 of us in that group. After we crossed over local hit 1500 in less than a minute so I assume there were many groups jumping at the same time. The comm chatter from ppl on-grid were reporting 30sec to 3 min response times on thier modules. Wepaons that were ungrouped and set to manual single fire seemed to have better luck. All we saw on our screen was the regular nebula/starfield background. Overview and fleet windows were empty. We could load character sheet, assets, etc. so we figured its not a database crash. After 10 mins we decided to go with plan as usual and dropped fleet to see if we could view/join our destination fleets. Fleet window let us drop fleet but it never let us search or create a fleet. Some of us tried to activate our defense modules but they never responded. Im assuming we were already dead at that point. Some of stayed to watch the local channel banter while others tried relogging. Of the ones that relogged it was about half and half either couldnt get to char selection screen, the other half could select char but were black-screened with full loading bars. Some gave up while others waited to see what would happen and after 1-2 hours were in thier medical clones. I was able to talk in local freely but corp/alliance/misc channels I could talk once every 30-40 seconds but seemed to see others talking at normal speeds. For giggles I logged on my alt and saw anything I said from DG was delayed 5-10 mins. I did see local hit 1700 beiefly before it went down..wished i had screen shot that. Once local dropped below 1400 I got a random damage message every few minutes but my shield dial didnt show anything until about 1300. Local in a matter of 2-3 minutes lost 300 people I started to register more damage and by the time system was below 1100 my ship was finally destroyed and I got my insurance mail and was able to read it. My dials never reloaded for the pod and in 5 minutes I got the clone activation mail and was back in my home system but still stuck but in my home system. I reloaded and instantly got back in and hopped in a new ship far away.
So from what we could tell anyone in space already before hitting the magic max number could play with mixed lag times. Software c oders I know seemed to think its a case of first come first serve. The nodes just couldnt divy out that many events to that many people at the same time. Players joining the nodes are just extra objects loaded in space which the server could handle. The players running those objects just were not inside the i/o queues limit to manipulae said objects or get notices of what was happening. This is also why those people did not see anyting happening to them until the number of i/o clients dropped to a level the node could queue up. Even if you logged out it would not have mattered, you were there until the node could process you not being there. As I was able to eventually see atleast the damage notices some buffers must have a sufficient capacity so I doubt its a buffer overflow/overwrite issue; those are what can cause crashes or code exploits. For the pilots that could play but reported random amounts of lag at the same times it could be assumed if the i/o queue theory is correct is this: Since the node was supposedly triple reinforced the there would be queues on each node. Pilots who were closer together in the queues would see less lag compared to others farther apart. |
Ravenariel
Caldari
BlazingAngels
|
Posted - 2010.01.29 21:47:00 -
[133]
-continued-
Did we just hit the limits of Infiniband, node capacity, or software? How is CCP going to address this? People are already calling this incident an exploit and others are talking to take advantage of it for the sake of griefing.
CCP you can not allow this to go on as-is if you honestly intend on protecting that which so many have worked hard for on your part, and us the customers.
|
Lorin Edehiel
Children of Gjallarhorn
|
Posted - 2010.02.01 20:45:00 -
[134]
Originally by: Numerenor
I am also considering canceling my account, along with 90 other people that i have been in contact with unless our very very expensive losses, are replaced and the game fixed as having your capitol fleet desotryed while your not even logged in , or waiting 3 hours for screen to load, totaly takes the Pi##
you are new to this game, arent you?
|
doseanator
|
Posted - 2010.02.03 21:13:00 -
[135]
No one on sisi (some 200+ pilots) can undock in FD. PLEASE HELP!!!
|
TheHolyJitaChecker
|
Posted - 2010.02.03 21:16:00 -
[136]
Directed toward CCP Tanis
Is there anyway your or CCP could mirror my current skills in TQ to the Sisi login? I am interested in doing some active testing, but the skill set that my Sisi login has is rather limited. Thanks for any help :) (the character I am speaking about is Noma L...)
|
Doc Fury
|
Posted - 2010.02.03 22:35:00 -
[137]
Originally by: Ravenariel
Did we just hit the limits of Infiniband
CCP would first have to be using Infiniband to hit its limit.
The accumulated filth of all their sex and murder will foam up about their waists and all the ho's and politicians will look up and shout 'Save us!' and I'll look down, and whisper 'no.' |
Abortica Inbortaliss
The United Snakes
IDLE EMPIRE
|
Posted - 2010.02.04 11:32:00 -
[138]
What if.. the problem was on our side.. In a new direction ---> Think of all the requests that get sent to the server at once and to the client for every drones velocity and specification of loading ship, or a 28.8 modem running a thanatos during a icestorm,
And.. My local internet provider has finally installed the software that knows when you are sending multiple requests and puts the Webifier on your laptop wrecking for half my battery life, shutting you down like it shuts down my utorrent lately. They've made the best MMO that has ever lived inside of a machine, is the server just stoned during the EPIC BATTLES of mass proportion cuz if so, it to could have been trapped in a bubble holding cloak.
|
|
|
| |
|
| Pages: 1 2 3 4 [5] :: one page |
| First page | Previous page | Next page | Last page |