insane:Talkiet: Slower routes don't always mean something's broken, and therefore, there may be no need to 'fix'.
There are many reasons traffic may not be taking the shortest route somewhere. Roading analogies again come in useful. If every single person took the shortest route in Auckland to work at peak time, there would be a LOT of wasted roading infrastructure not being used and the shortest routes would get congested, causing even bigger issues. Things work best when the traffic spreads itself around.
Internet - Same deal.
Cheers _ N
While technically you're not wrong, I think that traditional Telecom/GGI line of thinking is a bit out dated now. In the past users accepted whatever they got, today users have options and if some ISPs are willing to accommodate then it's only a matter of time before users will vote with their feet, and they should.
The last ISP I worked for at one point had really passionate network engineers, who so happened to be gamers who took it upon themselves to always ensure they engineered gaming traffic accordingly. It can be done, it just takes passion/creativity, and a attitude of enablement which looks for ways to improve things, not ways to justify the status quo.
And in this case, while you're not technically wrong either, it takes a lot more than that to sustainably do what you suggest - and its a lot easier for a small ISP to do it than someone with real scale.
Check my replies carefully - I have never denied that the optimisations have happened before, and they will continue to happen from time to time. However expecting that efforts will be made to optimise all games, all the time, for all users is not realistic.
I promise you the engineers in Spark (or VF for example) are just as passionate as those in [small isp] - but because they deal with orders of magnitude more users and traffic, they simply have to take a more controlled approach to this sort of traffic engineering.
When someone optimised WOT Asia traffic for example in [small isp], where did they record the change, the reason for the change, and what the traffic impact was? How will the next engineer know why that range has been plucked out of a much larger set of prefixes and sent the other way? Now, multiply that by a lot of games, and a lot of regions, and add in applications like Office 365, various voice and other apps - then consider how many of those may add (or delete!) prefixes from time to time. How are those changes picked up?
What you advocate is possible for sure, and on a small scale it's even a good idea. But as a general approach for a large ISP, is it a scalable and supportable solution? I'm not sure it is.
Cheers - N