On 8/7/16 2:40 , Ian Collins wrote: > On 08/ 7/16 04:51 PM, Ian Collins wrote: >> The zone on the new box had a cpu_cap of 100, so it was trying to run as >> a one core box... Which is what the "wait" states in prstat where >> telling me all along. >> >> Change that to 3200 and it builds in half the time as expected. > > One thing that did surprise me testing on his box is the software builds > significantly faster in a KVM than in an LX zone. The difference is > most noticeable with linking where one target takes well over twice as > long in the zone. > > KVM: > > $ time ninja bin/Posix_Debug/Tests > [1/1] LINK bin/Posix_Debug/Tests > real 1m3.693s > user 0m55.470s > sys 0m7.772s > > Zone: > > $ time ninja bin/Posix_Debug/Tests > [1/1] LINK bin/Posix_Debug/Tests > real 2m45.004s > user 1m35.427s > sys 1m7.567s >
Well, I'd probably start with two angles. The first is where do the microstates say you're spending your time during the link. Let's make sure there's no LAT on the scene. Otherwise, I might do something like profile where we're spending our SYS time and try and break that down further. Maybe just running the individual link command with ptime -m would be a good start. Robert ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
