[personal profile] robopet3
По следам разбирательств:
При наличии в кластере серверов с разными частотами процессоров можно получить проблему с Read Time Stamp Counter - RDTSC
Проблема выражается в резком падении производительности.
Описание тут:
https://communities.vmware.com/thread/154837
There is a known problem with RDTSC virtualization. By default, VMware virtualizes RDTSC but "monitor_control.virtual_rdtsc" option allows to disable RDTSC interception to improve time measurement resolution in VM. Disabled RDTSC virtualization may cause guest system to hangup at boot that is mentioned here:

http://www.vmware.com/pdf/WS6_Performance_Tuning_and_Benchmarking.pdf
http://www.vmware.com/pdf/vmware_timekeeping.pdf

Guest Windows hangs at boot because HAL timer initialization functions (HalpPmTimerScaleTimers, HalpScaleTimers) set TSC to zero several times to use its absolute value for time calculations instead of simply calculating the difference without resetting TSC. If RDTSC is virtualized, it returns a relatively small value because WRMSR (used to set TSC to zero) is virtualized too. If RDTSC is not virtualized, guest system receives host TSC value that is usually very big and cause divide overflow.

A recommended workaround is to start guest system with RDTSC virtualized, wait until it boots, suspend it, disable RDTSC virtualization then resume the VM. Since TSC is zeroed only several times at boot, guest can successfully use host TSC values later.

Причина проблемы - тут
Да мой старый laptop в несколько раз мощнее, чем ваш production server
https://habr.com/ru/post/496612/

Profile

robopet3

May 2023

S M T W T F S
 12 3456
78910111213
14151617181920
21222324252627
28293031   

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Feb. 22nd, 2026 12:59 am
Powered by Dreamwidth Studios