Testing gwan_linux32-bit (4.3.14) on a Digital Ocean VPS instance results in the CPU being maxed even when there are no http requests. The VPS instance has 1 core and 512 MB, running 32 bit CentOS 6.5. Below is some info about the CPU and kernel, and the gwan.log contents can be seen at http://pastebin.com/2UUeGRxn
When gwan is running (whether by ./gwan, or ./gwan -d, or ./gwan -d -w 1) , I can browse the provided sample pages/servlets with no apparent problems and the system appears to be stable. However, when I ssh into the vps, it is obvious that the CPU is maxed out. Observed load is between 2 and 3, the CPU is at 95% on average, and everything is sloooow in my terminal session.
I'd really like to run gwan, but this issue makes it a no-go for now. Is this purely a result of running under the KVM hypervisor? When might this issue be fixed?
$ uname -a Linux 2.6.32-4188.8.131.52.1.el6.i686 #1 SMP Fri Dec 13 11:45:23 UTC 2013 i686 i686 i386 GNU/Linux $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 2 model name : QEMU Virtual CPU version 1.0 stepping : 3 cpu MHz : 2299.996 cache size : 4096 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm up unfair_spinlock pni vmx cx16 popcnt hypervisor lahf_lm bogomips : 4599.99 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: