Novell EDIRECTORY 8.8 SP3, Руководство администратора, Страница: 560 / 634

560 Novell eDirectory 8.8 Administration Guide
n
ov
do
cx (e
n)
11
Ju
ly 20
08
NOTE: Ensure you reset ARC to non debug mode, i.e. set NDSTRACE = !ARC1 when you have
finished monitoring. Overhead printing costs are not desirable when you don't need it.
In the DSTrace or NDSTrace, you now see the individual referral costs displayed if Advanced
Referral Costing and +RSLV are turned on. The remaining tags are turned off using
set NDSTrace =nodebug
command.
Sorted results from DCAdjustCostAndSort follow:
137.65.10.3 cost of 217
137.65.10.9 cost of 222
137.65.10.10 cost of 400
The numbers change quickly if a remote server is slow or overloaded. The ExRef server's costing
adjusts dynamically every second, so to watch costs over time you should the trace to a log file.
18.5 Improving Bulkload Performance
eDirectory 8.8 provides you with new options to increase the bulkload performance.
The following are the tunable parameters for bulkload performance using the Novell Import Convert
Export (ICE) utility.
Š Section 18.5.1, “eDirectory Cache Settings,” on page 560
Š
Section 18.5.2, “LBURP Transaction Size Setting,” on page 561
Š Section 18.5.3, “Increasing the Number of Asynchronous Requests in ICE,” on page 561
Š
Section 18.5.4, “Increased Number of LDAP Writer Threads,” on page 562
Š Section 18.5.5, “Disabling Schema Validation in ICE,” on page 562
Š
Section 18.5.6, “Disabling ACL Templates,” on page 563
Š Section 18.5.7, “Backlinker,” on page 564
Š
Section 18.5.8, “Enabling/Disabling Inline Cache,” on page 564
Š Section 18.5.9, “Increasing the LBURP Time Out Period,” on page 565
Also refer to the various operating system tunable parameters.
18.5.1 eDirectory Cache Settings
The most common performance hits come from poor disk I/O management and the allocation of
insufficient memory for the eDirectory cache. If eDirectory is essentially the only application, you
can set the eDirectory cache to higher values with an upper limit of 2.5 GB. All allocated cache is
eventually used. eDirectory performance on highly volatile data is improved with more cache.
You can set the cache between 100 MB and 2.5 GB. You will generally not need more than three to
four times the size of the DIB. For large DIBs, limit the cache to 2 GB.