Zenst
Aliastra
   |
Posted - 2010.01.04 09:18:00 -
[1]
100 or even 500+ is not fleet battle testing now is it :(.
Seriously - why havnt CCP written a test harness to test this stuff out, do it once, record peoples action were you can then reply them to the server - thats how other people test server/client systems for robustness. WHen testing a http server do they get several hundred people to conenct to that web server, dont think so. How about you drag yoruselfs into the 90's on that at least.
Also until you start sorting out the whole log area you can expect little empathy for such testing. How hard would it be to have a client version of logs thats encrypted with a public key that only CCP can decrypt with a private key, that would be easy fix to the whole we cant except client log area and avoid the bull of outr log show nothing, yet at same time they dont show a valid action that leads to the end result you reaising the ruddy petition for.
So in summry:
Sort out a test harness that can test this or you will get what we pay for kind of results given the huge efforts needed in setting up test clients that then get updated the next day forcing you to do it all again. Whilst at it perhaps drag your bug system into reality as currently its about as useful as a shared notepad file that nobody else can read even when they have to write to it (sorry hope i didn;t devuldge inner working there, just observant).
Sort out client logs you can use - disraputed computing is not just processing offloading you know, think about it. Not exactly effort to do this in a simple/secure way.
If you did that instead of breaking things every ruddy time and then crying help then you only indicate that the live server is unable to log things at a level you can fix things with.
Also explain what the issue is - is it one big process loop thats spawns threads with a half-life that means most timeout before actioning once a certain level of users get in a system. Its a resource issue and were is that bottleneck - I/O thread starvation, beyond sloppy code were non the wiser.
Help us to help you and then when we do help, sort these very very simple things out I have outlined: test harness(record/replay clients) and trusted client logs, realy isn't major issue and I'd say a good programmer could knock up these in a very very short time, honestly.
|