Quoted By:
Reposting on this thread since >New Bread while I was writing it:
Devchama (Real) here, while I still refuse to get a tripcode you guys larping could at least put the bare minimum of effort to make it appear like you're me. In any case, to clarify what's going on: current theory is that when Market Closed occurs (I.E. server is archiving history) autotraders freak out. It used to not be as bad because the archiving was fast due to the smaller amount of trades but now >we are experiencing more trades than ever and, consequentially, the archival process will be slower. As the server is archiving, we're rejecting the requests but that still takes the server some effort. When a bunch of your autotraders stop receiving responses, regardless of the failsafes, BECAUSE all of the autotraders are failing simulatenously, they all start sending requests at the same time. This causes the server to bog more, thus extending that archival period. As this window opens, a bunch of other people's autotraders start spamming as the market isn't open and the server slows to a crawl, meaning that once the market opens, the confirmations for buys are slow to come out again, leading to more bogging down of the server. TLDR it's a failure caused by increased loads on our server around archival time, exacerbated by autotraders trading at the time which cascades into a full on failure as other traders start spamming the server. Yes, you can add a failsafe to the trader but it will never really *fix* this issue by itself because the issue is more the quantity of users autotrading at the time than an individual user's spam. At least that's my read of it.
