Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We have developed, and deployed, a web ERP for various small companies (less 30 users each one). Those who have cable connection don't experience any problems related with slow connections, but one is connected to the internet through 3 adsl lines using a peplink balancer to bond them all; this solution normally works, but when somebody upload a file to the ERP, all the connections from the office that are actually using the same adsl connection to the ERP experiment a lot of slow responses (I know this can happen in adsl connections).

The problematic office isn't able to use cable connection, or better alternative, so I'm asking about possible solutions (maybe from similar situations). Righ now, I think about these:

  • Change adsl routers by a better brand
  • Change the upload url to upload files with lower QOS
  • ¿Throttling in the client?
share|improve this question
Have you examined the traffic to se exactly what is happening during the file upload? What speed is the ADSL connection up/down? Does this happen if the Peplink balancer is removed or only one connection is used? –  Dave M Mar 6 '13 at 14:12
@DaveM the traffic in all http requests to our ERP. The ADSL is 8Mb download/500kb upload. It happens through those interfaces/wan/adsl routers that are being used to upload files. –  sucotronic Mar 6 '13 at 15:25
Have you examined the HTTP traffic with something like fiddler2 to see what is happening with packets from each system? –  Dave M Mar 6 '13 at 16:37
Traffic is normal, it seems like the modem is giving priority to the file upload instead of process each source at the same time. So, until the file upload finishes, the rest of connections seems hanged. –  sucotronic Mar 6 '13 at 16:43
@sucotronic: what are some of the details the app platform? Java/Apache, etc. –  Greg Askew Mar 6 '13 at 17:52

1 Answer 1

up vote 0 down vote accepted

Well, we've found a not optimal solution, but it works and avoid slowdown, and it's as follows:

  1. Modify all upload urls in your code in order to do all the file uploads to other port in the server. This way you can take advantage of the cookie to preserve the user login and other data in the requests.
  2. Implement in your code CORS to answer the OPTIONS petitions that the web browser is going to do when it tries to access other domain pages (yes, it's the same domain, but other port, and the browser consider it other domain :P).
  3. Configure apache in the machine to listen to the upload port
  4. Configure QOS in the routers/balancers to give the port you've assigned to upload files a lower priority than port 80.

The pity is that basic QOS settings available in all routers/balancers only are able to discern priority by ports, or other more lower level stuff.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.