Hello, all Eric, can you point to the location of such a cool tool like ADPerf? I've google'd but have got no results...
-- Best regards, Alex. ----- Original Message ----- From: Eric Fleischman To: [EMAIL PROTECTED] Sent: Sunday, May 09, 2004 5:22 PM Subject: RE: [ActiveDir] LDAP stress tool for AD 2003 I'll weigh in here a bit... I would argue there are lots of types of "stress" one can put on a DC and no single metric measures everything. In my brain, I typically first go through the following checklist of sorts to figure out what I'm looking at when testing a given DC: 0) Will the entire DIT on this DC be cached in memory - how much physical memory do we have? If dit<=2gb and ram>2gb, probably yes; if dit<=2.6gb and ram>3gb, are we using /3gb?; if 64bit, how much physical memory do we have (as that is the only limit really)? 1) What is functionality level of this domain (2k mixed or 2k native or 2k03 functional) and is the DC also a GC? 2) How many other domains in forest? 3) How many trusts to domains in other forests and downlevel domains? 4) What does the disk subsystem look like on this box? Where are dit and logs stored? After that is in mind, I ask myself this question: what is the most important thing this DC will be doing that need be finished quickly? For many DCs, the answer "authentication" probably comes to mind. For some others (say GCs servicing Exchange) queries (such as ANR) may be your answer. Still others might be some other application which it need satisfy. It just depends upon the box. Then, I look at the box and say logically "is this thing optimized for this scenario". That's hard for me to quantify really. ;) Now you indicated ldap calls specifically...within ldap calls we typically think of a few common things: 0) can the query be satisfied from info already in cache 1) is the query hitting solid indexes 2) within a "slow" query, there are fundamentally two reasons a query can be slow: a. cpu-bound (such as a large index intersection) b. i/o-bound (badly-designed search filter that need walk a lot of objects as it isn't hitting good indexes) With the info in those three items, there should be something painstakingly obvious to you: no single test can adequately measure each of these items. Further, any item from that list or my earlier list of "general things this DC does" can bog down the DC. We have some thresholds in place with default values that are typically good (for example, only 4 LDAP op's processed per physical CPU at a time by default, or perhaps for you MaxConcurrentAPI will be your bottleneck..I have no idea) to prevent swamping other subsystems, like I/O or secure channel. These things can be tweaked, but it's hard to give huge advice that is general enough to be of any use..that's what the defaults try to do. ;) I have seen boxes tuned to ANR before that got abused by a bad authentication setup and consequently, despite the amazing disk i/o subsystem and other things done, came to its knees due to some bad client requests and bad authentication configuration server-side. It's worth watching everything the box does. ADPerf is a great tool for this. If you give us some further insight in to the types of queries this box will be servicing we might be of more help. At least I think I might be. ;) ~Eric From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Mar-Elia Sent: Sunday, May 09, 2004 10:59 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] LDAP stress tool for AD 2003 There is a load test tool for AD, called ADTest. Check it out at: http://www.microsoft.com/downloads/details.aspx?FamilyID=4814fe3f-92ce-4 871-b8a4-99f98b3f4338&DisplayLang=en -----Original Message----- From: [EMAIL PROTECTED] on behalf of Tony Murray Sent: Sun 5/9/2004 8:40 AM To: [EMAIL PROTECTED] Cc: Subject: RE: [ActiveDir] LDAP stress tool for AD 2003 Hi Steve I'm not aware of anything specific. The ldclt tool (comes with iPlanet) might also work for AD, but I haven't tried it. Being an ASP.NET guru you should be able to script something quite easily :-) You can track expensive and inefficient queries (good for a stress test) by using the method described in the link below. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnactdi r/html/efficientadapps.asp Also be aware that the LDAP policies in place on the DCs will protect the DC to a certain extent. For example, the maximum number of records returned for a single query is 1000, although you can change these by modifying the MaxPageSize policy or by paging the results using the pagedResultsControl LDAP control. Tony From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Schofield Sent: Sonntag, 9. Mai 2004 16:07 To: [EMAIL PROTECTED] Subject: [ActiveDir] LDAP stress tool for AD 2003 i have a need to find a tool that will help stress test LDAP calls to AD. Anyone aware of a tool such as this? I know in the web world MS has WAST (web app stress tool), exchange has JETSTRESS, LOADSIM. Steve Schofield [EMAIL PROTECTED] Microsoft MVP - ASP.NET http://www.deviq.com List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
