Well to be fair the ddos attacks are not the only issues at hand, it is also the very bad coding and the not so great servers SE still use, lol
Granted yes ddos attacks are not a SE thing but we still have issues from time to time when not attacked


Well to be fair the ddos attacks are not the only issues at hand, it is also the very bad coding and the not so great servers SE still use, lol
Granted yes ddos attacks are not a SE thing but we still have issues from time to time when not attacked




SE's back end is pretty standard. Most databases can only handle about 5000-10000 connections at once, which is why SE's server cap is 5000 players at a time, with the lobby server slowing things down to 100 new connections per minute. The servers themselves are pretty stable, only crashing completely once ever few weeks. When it's their fault, SE admits it was a "server programming error" in the recovery notes, usually some bug that caused a memory leak or somesuch.
The network infrastructure itself isn't that great, but again it's also industry standard. Every character is a constant query upon 3-4 servers as we navigate between duties, instances, party finder, etc. They could lift the query cap on the database, but past experimentation has found that the database gets gummed up at 5000+ characters, and that matches my own experience in a development environment whereupon a relationship database chokes and dies beyond 10,000 simultaneous queries. We keep our Oracle databases capped at 10K as well.



Actually there are many systems that handle many more connections and DB queries with ease. For the stuff I worked on most of my career having 20K-50K concurrent users per image was not uncommon. I also worked with some large database design and we could easily get well beyond 10K transactions per second. It typically isn't the DB or operating system software that is the limiting factor but the hardware and application itself. Given the little I know about FF XIV's environment I would say they are hardware constrained and some of that constraint is due to poor application design. I would also say some of the hardware constraints are also based on how much SE is willing to spend in relation to profit margins. So forgoing the DDoS issue which is not their problem SE could probably improve game performance if they were willing to invest in it.SE's back end is pretty standard. Most databases can only handle about 5000-10000 connections at once, which is why SE's server cap is 5000 players at a time, with the lobby server slowing things down to 100 new connections per minute. The servers themselves are pretty stable, only crashing completely once ever few weeks. When it's their fault, SE admits it was a "server programming error" in the recovery notes, usually some bug that caused a memory leak or somesuch.
The network infrastructure itself isn't that great, but again it's also industry standard. Every character is a constant query upon 3-4 servers as we navigate between duties, instances, party finder, etc. They could lift the query cap on the database, but past experimentation has found that the database gets gummed up at 5000+ characters, and that matches my own experience in a development environment whereupon a relationship database chokes and dies beyond 10,000 simultaneous queries. We keep our Oracle databases capped at 10K as well.
I just want to add onto the DDoS attacks a bit. While SE is using NTT for their backbone access it is important to realize they are not the only backbone provider to be attacked. L3 has also had DDoS problems over this same period of time. L3 also had a routing error that affected Comcast customers during this same time frame. So the current problems really are beyond the control of SE.


SE servers were upgraded in the move, the hardware isn't a bottleneck in this issue. The game's back end is horribly antiquated but also irrelevant to this issue. The problem is with the connection between the datacenter and customers; the game itself has remained fairly stable during this. So to be fair, this is not SE fault and we deserve no compensation from them.


And i never said i wanted compensation.lolSE servers were upgraded in the move, the hardware isn't a bottleneck in this issue. The game's back end is horribly antiquated but also irrelevant to this issue. The problem is with the connection between the datacenter and customers; the game itself has remained fairly stable during this. So to be fair, this is not SE fault and we deserve no compensation from them.
I thought for sure all they had done is move the servers, i guess i never read that they actually upgraded them.
I still think they could of left servers in Montreal and have more in Cali. My connection was so much better with it being in Montreal





They did not move the servers, there is no way to move racks of servers over 3000 miles, and have them tested and up and running in 24-48 hours.And i never said i wanted compensation.lol
I thought for sure all they had done is move the servers, i guess i never read that they actually upgraded them.
I still think they could of left servers in Montreal and have more in Cali. My connection was so much better with it being in Montreal
The reason they moved their DC out of montreal in the first place was due to electrical problems. The servers were overcapacity, and the DC could not provide stable power any longer.
Seems kind of odd when you think about it. Last time there was a DDOS attack every server was being effected, now it seems some people are affected it could be a DDOS. I doubt is SE most likely its local/user net connection/band being congested. Some internet companies throttle their connection based on usage/time of day/ hot zone location/. It could also be do to multiple users sharing a line that can cause those DC. I use to have that problem back in the day until I said EF it, got an individual line for my gaming. It's rare I even see any lag now. If it does DC is normally do to internet company issue. Coding may have something to do with it in the back end true, not likely though in this situation.
Last edited by ManuelBravo; 11-14-2017 at 12:45 AM.




It's pretty well established at this point that it is a DDoS attack. The difference between the DDoS at Stormblood's launch and now is that this time FF14 is not being directly attacked. They are attacking SE's ISP, which is why only users in certain areas are having issues and why it's not just FF14 that is being affected. And also why SE is not responsible and "owes" us, the customers, nothing. The last 10 pages of this thread have repeated this ad nauseam.
Last edited by Rymm; 11-14-2017 at 12:03 AM.
~ My FF14 IG account ~
https://www.instagram.com/rymmrael/
~ Interesting FF14 fan creations to check out ~
https://aetherflowmedia.com
http://www.eorzeasntm.org/

I don't think SE "owes" us anything, and it doesn't really sound like most people suggesting this think that either. At some point there comes a time that regardless of the reasons this isn't SEs fault, people will start dropping subs. Just from my own experience it's rare that I can go 30 minutes in an instance without seeing a couple big spikes where half the group shows as DCing. Again, it doesn't matter if it's SE's fault or not, at some point people just won't want to deal with it.It's pretty well established at this point that it is a DDoS attack. The difference between the DDoS at Stormblood's launch and now is that this time FF14 is not being directly attacked. They are attacking SE's ISP, which is why only users in certain areas are having issues and why it's not just FF14 that is being affected. And also why SE is not responsible and "owes" us, the customers, nothing. The last 10 pages of this thread have repeated this ad nauseam.
Point is SE does not owe us anything,. It is placed in their terms of use. We all pay our subscription and we are all vulnerable to this situation. People need to stop bitching and realize in the online gaming world this is to be expected. I never said they owe us anything. If anything I have mention this prior,It's pretty well established at this point that it is a DDoS attack. The difference between the DDoS at Stormblood's launch and now is that this time FF14 is not being directly attacked. They are attacking SE's ISP, which is why only users in certain areas are having issues and why it's not just FF14 that is being affected. And also why SE is not responsible and "owes" us, the customers, nothing. The last 10 pages of this thread have repeated this ad nauseam.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

Reply With Quote


