3 ms·
Sometimes that requires expertise in a very low-level topics. For example I've read a similar story, but developer digged the truth. Production was running on v
by vbezhenar 7y ago
Sometimes that requires expertise in a very low-level topics. For example I've read a similar story, but developer digged the truth. Production was running on vmware cluster with live migration or something like that. Servers used slightly different CPUs (frequency differed a bit), so VMware emulated some important instruction (something related to get current timestamp). MSSQL used that instruction a lot in one specific scenario, so it was running much slower on virtualized production server.
They were able to figure it out and rewrote one stored procedure so it ran fast again. But I'm sure that I, for example, don't possess the necessary expertise to figure this out. I wouldn't be surprised that in many small-to-medium companies there are no experts of that level either.
- gvjddbnvdrbv 7y agoI would never get the CPU instruction bit but I'd like to think I'd get as far as the stored proceedure.
- xxs 7y agoTime Stamp Counter (TSC) has been trapped to make sure it returns the same value across all cores. Intel fixed that part, though.
- zorked 7y agoIn a live migration scenario the TSC in the source and destination machines will be necessarily different so that emulation is required to make it not warp. That said, due to previous TSC instability all operating systems deal with a TSC warp pretty well. Whether applications deal well with it is probably the reason why emulation is the default, but it could be that this can be disabled. (Everything AFAIRC)
- vardump 7y agoSure, across all cores on a physical CPU socket. But not across CPU sockets.
- RedShift1 7y agoProbably VMware fault tolerance which keeps a virtual machine in sync over 2 physical machines to allow instant failover. But I can imagine that taking a lot of instruction trapping.