edir on multiple processors


I admit I am sure I must have researched this years ago :) But this was
pre SP8 which I know a lot of performance and scalability was
introduced.

So I am wondering does edir prefer multiple processors? I run on single
core VM, and am not cpu constrained at all, I am just curious.


--
mtsjej
------------------------------------------------------------------------
mtsjej's Profile: https://forums.netiq.com/member.php?userid=6351
View this thread: https://forums.netiq.com/showthread.php?t=53252

Tags:

  • eDir is multi-threaded, so it will take advantage of any processors you
    have if given enough load, yes.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
  • On Thu, 02 Apr 2015 20:24:01 0000, mtsjej wrote:

    > I admit I am sure I must have researched this years ago :) But this was
    > pre SP8 which I know a lot of performance and scalability was
    > introduced.
    >
    > So I am wondering does edir prefer multiple processors? I run on single
    > core VM, and am not cpu constrained at all, I am just curious.


    You know, I never really considered whether that would help or not. My
    instinct is that it probably doesn't care too much, since the performance
    bottlenecks tend to be network-bound rather than CPU-bound (eDir itself
    doesn't do a lot of heavy-duty data processing). It might be interesting
    to put a load on it (request-based, not write-based, because the writer
    thread is, as I recall, single-threaded) and see if it uses more than a
    single core.

    It is multithreaded, so in theory, it probably would, as long as it's not
    a write-bound load.

    Just sitting not processing requests, though, it shouldn't consume a lot
    of CPU at all.

    Jim

    --
    Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
    Novell/SUSE/NetIQ Knowledge Partner

  • Thank you. I am not cpu bound, I was just curious. I don't want to give
    it processors, if it does not need it, it could slow it down with having
    to keep track of all new threads and stuff. I am sure you are correct in
    that generally most bottlenecks will occurs with writing.


    --
    mtsjej
    ------------------------------------------------------------------------
    mtsjej's Profile: https://forums.netiq.com/member.php?userid=6351
    View this thread: https://forums.netiq.com/showthread.php?t=53252

  • On Thu, 02 Apr 2015 20:42:12 0000, Jim Henderson wrote:

    > On Thu, 02 Apr 2015 20:24:01 0000, mtsjej wrote:
    >
    >> I admit I am sure I must have researched this years ago :) But this was
    >> pre SP8 which I know a lot of performance and scalability was
    >> introduced.
    >>
    >> So I am wondering does edir prefer multiple processors? I run on single
    >> core VM, and am not cpu constrained at all, I am just curious.

    >
    > You know, I never really considered whether that would help or not. My
    > instinct is that it probably doesn't care too much, since the
    > performance bottlenecks tend to be network-bound rather than CPU-bound
    > (eDir itself doesn't do a lot of heavy-duty data processing).


    Sync traffic can use different algorythms, depending on how many
    processors are available.

    If you add IDM to the mix, multiple threads are started for each driver,
    so lots of CPU cores and horsepower can be helpful.


    --
    --------------------------------------------------------------------------
    David Gersic dgersic_@_niu.edu
    Knowledge Partner http://forums.netiq.com

    Please post questions in the forums. No support provided via email.
    If you find this post helpful, please click on the star below.
  • On 04/03/2015 07:57 AM, mtsjej wrote:
    >
    > Thank you. I am not cpu bound, I was just curious. I don't want to give
    > it processors, if it does not need it, it could slow it down with having
    > to keep track of all new threads and stuff. I am sure you are correct in


    eDir has, by default, dozens of threads allocated; if any software really
    has problems taking care of idle threads it should probably be tossed out,
    and eDirectory does not fall into this category. It has been
    multi-threaded for as long as I can remember, which means back at least
    until 2004.

    > that generally most bottlenecks will occurs with writing.


    As always, the biggest bottleneck for a computer is I/O to a spinning
    disk; SSDs help, and cache (which eDir and Linux both use) helps.
    Otherwise tuning issues always come in the form of missing or
    incorrectly-defined indexes, lack of replicas, or applications trying to
    do things very poorly causing excessive work for eDirectory. There is a
    tuning guide from NetIQ that you may enjoy reading.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...