Monthly Archives: September 2015

Wahey! UCDay! Hooray!

So… I’m properly honoured to have been selected to present at UCDay on the 28th of September. I’m really excited because it’s been quite some little while since I’ve done this sort of thing – decades rather than years! Hopefully I’ll not let myself down too badly, eh?

What is UCDay? It’s the UKs only independent Microsoft unified communications technical conference focussing on Skype, Office 365 and Exchange; basically a day of sessions from some of the best technical presenters in the world (and me). People like Michael Van Horenbeeck, one of my favourite technical authors, and Brian Reid, who delivered the hardest three days of training I’ve ever had in my life during my MCM rotation. Pretty much every speaker is an MVP, an MCM or an MCT; in the case of Gary Steere, all three. There’s 18 sessions to choose from, in three tracks; Skype for Business, Office 365 and Exchange. This conference is worth every penny, especially as it’s FREE.

So, what am i going to do? Basically a session on designing Exchange for shared services – how simplification and repeatable design units reduced the number of support calls we generated. Why is that of interest to anybody? Because if it reduced support costs for us, it will reduce support costs for other people too (probably). There’s no magic – it’s just following good design and documentation practices, but with some real world figures to reinforce the common sense. There’ll be a little bit on how (i hope) we’re going to apply it to Exchange 2016, a little bit on how it can be extended to other applications. I hope people find it interesting.

The conference is at the National Motorcycle Museum near Birmingham Airport on 28th September. I’d thoroughly recommend anyone with an interest in Exchange, Office 365 and Skype for Business to attend. I’d be there even if i wasn’t speaking.

There’s also a quiz the night before. shriek. I LOVE quizzes. my two favourite answers are “Tavares” and “goldcrest”.

Advertisements

What difference does hyperthreading make to a VMWare guest cpu config?

There is some controversy in the Lync world at the moment regarding hyperthreading when virtualising. do you follow Microsoft’s advice, and turn hyperthreading off at the host level? VMWare would much prefer you didn’t actually. in Exchangeland, the compromise was reached some time ago; you turn it ON at the host, but turn it OFF at the guest. we will now pause for a brief torrent of dispute. this depends on you having very little cpu contention – if you have cpu contention, you will end up increasing the amount of cpu ready time while the esx scheduler waits for physical cpus to become available – in other words, in an oversized environment, this is best. if you have undersized, then guess what, you’re stuck with leaving hyperthreading enabled at the guest level. Sizing correctly is key – size for the physical cpu cores in your host, and add up all the exchange servers on the host. so if you physically have 2 hex core sockets, you have 12 vcpus to allocate to Exchange servers on that host. no more. enabling hyperthreading doesn’t make any difference here. but that’s off the point*. i was asked “what difference does turning off hyperthreading make to the guest, nick? will SQL lose a scheduler? will it all go horribly wrong in my guest?” so here is the answer.

 

no difference.

no.

and no.

 

and here’s the proof.

this is an edge server in one of my labs. it has 2 sockets, with two cores each. HT is enabled at the HOST level as well.

image

yeah, i know. that’s a really dull way to set stuff up.

image

hyperthreading is set to “any” in the guest. what does this look like inside the guest?

image

image

which is, i’d hazard, exactly what we’d expect.

 

i was asked how this differed if we disable hyperthreading at the guest level. so…

clip_image001

 

and…

image 

image

 

exactly the same. which is, of course, what you’d expect. but it’s nice to have proof, right?

 

 

*do you know what else is off the point? if you have 2 hex core sockets in your host, you’re likely to hit some issues when you try to avoid those NUMA boundaries, aren’t you? Exchange is sized for multiples of four.