search for: 254ms

...Direction = To Switch, From = 3230 at 172.16.8.40, To = 1042 at 172.16.8.5 08-14-13 07:30:14 AM-253ms Line = 18, Channel = 1, SIP Message = Response, Call Ref = 152, Direction = From Switch, From = 3230 at 172.16.8.40, To = 1042 at 172.16.8.5, Response = 487 Request Terminated 08-14-13 07:30:14 AM-254ms Call Ref = 152, Originator State = Clearing, Type = Trunk, Destination State = Alerting, Type = User 08-14-13 07:30:14 AM-254ms Call Ref = 152, Disconnect from Originator End -- rickygm http://gnuforever.homelinux.com -------------- next part -------------- An HTML attachment was scrubbed......

...e is still not really ready yet. > * Tests > - Migration time improvement > Result: > Live migration time is reduced to 14% with this optimization. > Details: > Local live migration of 8GB idle guest, the legacy live migration takes > ~1817ms. With this optimization, it takes ~254ms, which reduces the time > to 14%. > - Workload tests > Results: > Running this feature has no impact on the linux compilation workload > running inside the guest. I think you should try something memory intensive. Try asking qemu migration guys for hints on a good test to run....

...sor and transferred in the next round if they are used and written. * Tests - Migration time improvement Result: Live migration time is reduced to 14% with this optimization. Details: Local live migration of 8GB idle guest, the legacy live migration takes ~1817ms. With this optimization, it takes ~254ms, which reduces the time to 14%. - Workload tests Results: Running this feature has no impact on the linux compilation workload running inside the guest. Details: Set up a Ping-Pong local live migration, where the guest ceaselessy migrates between the source and destination. Linux compilation, i.e....

...sor and transferred in the next round if they are used and written. * Tests - Migration time improvement Result: Live migration time is reduced to 14% with this optimization. Details: Local live migration of 8GB idle guest, the legacy live migration takes ~1817ms. With this optimization, it takes ~254ms, which reduces the time to 14%. - Workload tests Results: Running this feature has no impact on the linux compilation workload running inside the guest. Details: Set up a Ping-Pong local live migration, where the guest ceaselessy migrates between the source and destination. Linux compilation, i.e....

...isor and transferred in the next round if they are used and written. * Tests - Migration time improvement Result: Live migration time is reduced to 14% with this optimization. Details Local live migration of 8GB idle guest, the legacy live migration takes ~1817ms. With this optimization, it takes ~254ms, which reduces the time to 14%. - Workload tests Results: Running this feature has no impact on the linux compilation workload running inside the guest. Details: Set up a Ping-Pong local live migration, where the guest ceaselessy migrates between the source and destination. Linux compilation, i.e....

...sor and transferred in the next round if they are used and written. * Tests - Migration time improvement Result: Live migration time is reduced to 14% with this optimization. Details: Local live migration of 8GB idle guest, the legacy live migration takes ~1817ms. With this optimization, it takes ~254ms, which reduces the time to 14%. - Workload tests Results: Running this feature has no impact on the linux compilation workload running inside the guest. Details: Set up a Ping-Pong local live migration, where the guest ceaselessy migrates between the source and destination. Linux compilation, i.e....