Report this

What is the reason for this report?

Amsterdam server processing speed seems very slow but bandwidth is fine.

Posted on June 18, 2013

Doing anything like apt-get update seems to be taking an absolute age. I did a wget -O /dev/null - http://cachefly.cachefly.net/100mb.test and got 30mb/sec, and average speeds for apt-get downloads seemed about 12mb/sec so the problem isn’t there.

But even things like htop, which is just a slightly more advance “top” show as taking 10% of my CPU allowance. It takes a good 5 seconds to show the “welcome” message, when my previous non-SSD basic VPS was completely instant (for comparison, htop either doesn’t show at all, or takes just 1% CPU on the other VPS).

My details are 512MB Ram 20GB SSD Disk Amsterdam 1 Ubuntu 13.04 x64 Server

In the admin setup log, it says it took 115 seconds to provision; as this is 2x as long as it suggests it should take, I’m wondering if there are some issues with that machine or region?

BTW, I rebooted the machine before I started typing this, after giving it some virtual memory (as required by the Dropbox linux client) same as I have with other VPS, and 5 minutes later I’m still getting “connection refused”. I’d normally expect a reboot to take around 20 seconds on a VPS.



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Correct @jonathan. We recommend opening up a support ticket as it will help up determine the issue better in this case.

Update - thankfully I found the Virtual Console (shame you can’t copy/paste) but basically it seemed to be “stuck” at <br> <br>"Killing all remaining processes … [fail]. <br>“Will now switch to single-user mode. <br>Give root password for maintenance or type Control-D to continue”. <br> <br>Giving root password just brought me back to the root@www prompt. <br> <br>Entering “reboot now” just repeats the “Killing all remaining processes … [fail]” message. <br> <br>Had a google and found this: http://ubuntuforums.org/showthread.php?t=2139160 <br> <br>So basically, “reboot now” shouldn’t be used with 13.04. I’ll post another thread to help others! <br> <br>So I’ve got my machine back but it seems now quicker. I fired up a new droplet in NYC and it’s LOADS quick but as I’m in Europe having AMS working at full speed would be preferable.

Second update: Looking at twitter, it seems other are having problems with Amsterdam for at least 5 days now. DO twitter support say to open Amsterdam slowness problem tickets with “urgent” status, so that’s what I’ve just done. Hoping that I can configure my NYC droplet and then move to AMS once fixed…

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.