Pretty sure it's that the various sizing calculators from Microsoft always base
figures on physical/actual number of cores. When you introduce HT, you're not
really giving yourself double the number of CPUs in raw performance, so any
planning based on the calculators goes out the window.
We
http://blogs.technet.com/b/jeff_stokes/archive/2010/09/15/to-hyper-thread-or-not-that-is-the-question.aspx
The issue with HT is that, since it is scheduled as separate processor, but
doesn't have unique cache assigned to it, in certain memory intensive
operations it can cause reduced
Thanks for the responses. I can appreciate the technical reasoning that
Michael pointed out, but I'm also curious if this reasoning holds true with
current Westmere or Sandy Bridge chipsets.
In regards to the recommendation from Microsoft, it comes across as if they
don't trust the person
Thanks for the feedback. We'resupporting just over 2000 mailboxes in this
environment so we felt memory configurations were sufficient.
- Sean
On Wed, Sep 5, 2012 at 5:14 PM, pramatow...@mediageneral.com wrote:
We have 6500 mbx, ~2G worth in them, 6 servers in two sites, 3 active DB's
on each
CAA?
Regardless, if your issue is the one of which I am thinking, then redirecting
to a specific CAS is the proper solution.
-Original Message-
From: Maglinger, Paul [mailto:pmaglin...@scvl.com]
Sent: Thursday, September 6, 2012 12:50 PM
To: MS-Exchange Admin Issues
Subject: PST import
Client Access Array.
-Original Message-
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Thursday, September 06, 2012 12:04 PM
To: MS-Exchange Admin Issues
Subject: RE: PST import problem not fixed yet?
CAA?
Regardless, if your issue is the one of which I am
Is your Outlook client looking to the Contacts rather than the GAL? Outlook,
Address Book, Tools, Options?
From: Tanya Pinetti [mailto:tpine...@outlook.com]
Sent: Thursday, September 06, 2012 12:32 PM
To: MS-Exchange Admin Issues
Subject: Outlook Does Not Resolve Check Name
Our Exchange Global
Oh. It happens because RPC_IN and RPC_OUT channels get confused. My
understanding is that on smart LBs you can do some extra affinity checking, but
I haven't looked at it in detail, because redirecting to a single CAS is much
easier.
Insofar as it being fixed - I have no clue. Exchange 2013
Sorry for confusion. That's the lingo that was used in my documentation.
So now I'm curious... Does this mean that by keeping it pointed at the CAA
there could be other problems crop up, not necessarily with PST migration?
Should I not change the setting back when I'm done (so if the CAS I
It is set to Start with Global Address List.
From: pmaglin...@scvl.com
To: exchangelist@lyris.sunbelt-software.com
Subject: RE: Outlook Does Not Resolve Check Name
Date: Thu, 6 Sep 2012 17:57:33 +
Is your Outlook client looking to the Contacts rather than the GAL? Outlook,
Address
See, I don't get to see internal documents. :-) But as far as I know, this is
only an issue when you have lots and lots of connections open from a single
task. That shouldn't normally happen.
-Original Message-
From: Maglinger, Paul [mailto:pmaglin...@scvl.com]
Sent: Thursday,
Gotcha. Like I said, it got me thinking. I hope they look at doing something
about this for 2010. I'm not keen on it's fixed in the next full version
solutions. I get enough of that from Ci*co. :-)
Thanks for your insight Michael.
-Paul
-Original Message-
From: Michael B. Smith
Okay, here's the issue. I had a server crash in one of my sites that contained
one of my public folder stores in Exchange 2010. I had a replica in the same
site and moved all of the databases to point to it. My issue is that there are
a bunch of messages stuck in the queue trying to get to the
Ah. Yeah, I posted all that excess just to say what we had, how it was
configured, and so on. I understand the reasoning behind not using HT (and know
I don't
*have* 24 procs). Just lucky enough that we never ran into problems using it
configured that way:)
Cheers,
Paul
Blackberry
From: Sean
14 matches
Mail list logo
