Tag Info

New answers tagged

1

If you're going the route of high performance typically you'll want to run as few other (scheduled) processes as possible as they'll interfere with your application. Linux, like the classical UNIX operating systems, is designed to run multiple applications concurrently in a fair way and tries to prevent resource starvation and you'll be aiming for the ...


3

Honestly, I wouldn't be using Ubuntu for this... but there are options that can be applied to any Linux variant. You'll want to increate your network stack buffers: net.core.rmem_default = 10000000 net.core.wmem_default = 10000000 net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 If the application is writing to disk, maybe a scheduler/elevator ...


2

Upgrade your server I know you don't want to hear it. I know you client doesn't want to hear it. But it's what you need to hear! If the client is running 4 websites (production no less) they should fork out some cash for a better server. But why? micro instances are NOT designed for production use (AWS says so themselves), they suffer from contention, ...


1

According to top, it looks like something is using up a good amount of CPU. Update your post with the process list according to top. More than likely, something is pulling a lot of I/O on the server and exhausting RAM as most of your swap is cached (so, recently used). The load should not be that high on a healthy server.


1

Start by tracing what is taking too long with Chrome/IE developer tools (network tab). Confirming that the slowness is happening for all requests irrespective of type, trace the path from end user to your server (traceroute) looking for any excessive delays. Test from multiple places. On the server, check the number of open connections (netstat -antp | ...


0

I know you didn't ask for DB related things, but I still have to mention this. Your tables should use InnoDB as the engine. The problem with MyISAM is that it has only table-level locking. That is, if you insert data to the table, the whole table is locked, and other queries have to wait for the operation to finish before they can proceed. With InnoDB, the ...


0

First, having this query to run on only one CPU is normal. Your problem is likely that the database will be occupied with INSERTing your data into the tables and doesn't have time or I/O capacity left to handle SELECT queries to display your site. One approach you can try is to break down the import data as much as possible and use INSERT LOW PRIORITY or ...


0

Scale horizontally, not vertically. Instead of having one server do all of the work, setup many to do the same. They may not all host the same data, which allows a smaller set to access. Hadoop may be one way to do this. Another could be just in the way it's coded. putting a lot of little servers behind varnish would definitely be something that could help ...



Top 50 recent answers are included