Tag Info

New answers tagged


What you describe is not possible. Buy a computer with the fastest CPU you can find (number of cores/threads is unimportant).


If the data, that the application processes can be divided into smaller packs, you can run multiple copies of the application, each processing part of the data and then try to put together the result (i.e. with a script).


I have never experienced issue such as long load times like that, however one thing I have noticed that tend to speed up my Wordpress load times is to use WP Super Cache. It caches the pages as plain HTML pages for most users, that way your server doesn't need to recompile the page every time. As others have said, it could be poor server performance on ...


I'm afraid your experience is clearly insufficient to deal with such issues. You probably should hire someone to either supervise the server for you, or at least get it straight now (and get rid of cPanel). He might even tell you it is not a server issue, but rather WordPress thing. You should start with looking at the load itself (CPU, memory, I/O, etc., ...


To me it looks like that the plugin does simply so heavy processing for every request that the requests take such a long time. You should ask the plugin provider if they can explain the slowdown in any way.


You might know what a core is from shopping for desktops and laptops. It's the CPU, the processor, the bit that does the work. Here's a wikipedia link that might help. I plugged your site into this tool and most of the complaints were CSS and javascript that had to fully download before your site could fully render. Of course, I imagine we're viewing the ...


I have made a chart for each NUMA node affinity. Hope someone could benefit from it.


I actually wrote three comments but it is basically an answer. Your CPU reads stuff from buses, suppose it is reading from RAM, if it isn't in the cache the CPU (well they used to, now they're not so linear - but can be thought to: ) stall and literally do nothing while the lower IO parts of your CPU put the address on the addr bus, and wait for the RAM to ...


I'm not 100% sure I understand the question, but there's some ideas. There's another question here that asked this, and has some good answers: Can anyone explain precisely what IOWait is? There's a good post here: http://veithen.github.io/2013/11/18/iowait-linux.html


The CPU idle status is divided in two different "sub"-states: iowait and idle. If the CPU is idle, the kernel then determines if there is at least one I/O currently in progress to either a local disk or a remotely mounted disk (NFS) which had been initiated from that CPU. If there is, then the CPU is in state iowait. If there is no I/O in progress that was ...


I suppose you machine is a VM? Then, you might see these peaks due to the hardware's resources where your machine is running on. I guess that it is a syswait or iowait type of peak, where your machine has to wait for the virtualization host to complete its task(s). In this case, you won't see a thing in htop/atop/... since you machine is actually not ...

Top 50 recent answers are included