Eddie Lien
New Member
Hi,
I have a new installed WCS5 in google cloud, and it takes about 25 minutes to startup the real wcs process.
I've read the case
https://forum.flashphoner.com/threads/observation-of-very-long-startup.10655/#post-10886
and found it seems similar but not the same, my cpu is Intel Xeon.
Anyone has solution for this?
My WCS build version is v.0.5.19.2241 - 5.0.2318
And my server information:
I have a new installed WCS5 in google cloud, and it takes about 25 minutes to startup the real wcs process.
I've read the case
https://forum.flashphoner.com/threads/observation-of-very-long-startup.10655/#post-10886
and found it seems similar but not the same, my cpu is Intel Xeon.
Anyone has solution for this?
My WCS build version is v.0.5.19.2241 - 5.0.2318
And my server information:
Code:
$uname -a
Linux wcs-use 3.10.0-514.21.2.el7.x86_64 #1 SMP Tue Jun 20 12:24:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ java -version
openjdk version "1.8.0_131"
OpenJDK Runtime Environment (build 1.8.0_131-b12)
OpenJDK 64-Bit Server VM (build 25.131-b12, mixed mode)
$ cat /proc/meminfo
MemTotal: 11271716 kB
MemFree: 9610768 kB
...(ignored)...
$ cat /proc/cpuinfo
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 62
model name: Intel(R) Xeon(R) CPU @ 2.50GHz
stepping: 4
microcode: 0x1
cpu MHz: 2500.000
cache size: 30720 KB
physical id: 0
siblings: 6
core id: 0
cpu cores: 3
apicid: 0
initial apicid: 0
fpu: yes
fpu_exception: yes
cpuid level: 13
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc eagerfpu pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c rdrand hypervisor lahf_lm fsgsbase tsc_adjust smep erms xsaveopt
bogomips: 5000.00
clflush size: 64
cache_alignment: 64
address sizes: 46 bits physical, 48 bits virtual
power management:
...(ignored)...