Why should an MPLS be slower when opening databases?
Posted on 2014-01-30
I've had an MPLS installed between two sites 15m apart. I used to use two leased lines joined by a Vpn but I was told that MPLS technology was much faster as it eliminated the Watchguard units we had and was directed over a private line not the general internet. In practice it's no faster at all.
Previously users had connected to the other site via a terminal server and opened their databases from there. I was hoping that I'd be able to do away with one of the terminal servers and save the users having to logon twice whenever they used a program at the other site. When I tried opening some of the databases directly over the p-wan they were noticeably slower than when used locally. Both leased lines are 10Mb so I thought I would try changing the speed of the network card on one PC down to 10mb to see how slow that would be. It was a little slower than when using the default 1Gb speed but not much. For example, the slowest database we have is a personnel system that uses Pervasive SQL. On a 1gb connection it takes 10secs to open. On a 10mb PC it takes 15 secs to open. From a 1gb PC at the other site over the P-wan it takes 4 minutes to open.
The comms company who supplied the link have done all sorts of tests and assure me its running at its correct speed and there is nothing in their firewall that is restricting any internal traffic. But the database company has hundreds of sites and have never heard of this before. It is also slow with a more modern fundraising system running in SQL server 2008 although nothing like so bad as the personnel system.
Can anyone explain why a 10mb mpls should be so much slower than a 10mb PC running locally? No one has been able to give me any explanation so far.