We think of the transaction time with LDAP as being very
fast, and it is; but when you deal with so many transactions, general queuing theory and
rendering speed tend to get the better of us. A read from RAM is simply much faster than
a transaction to LDAP.
This view is supported with the lazy loading (Grand, 1999) dynamic LDAP cache. At least three
levels of the chain already exist, and the subsequent entries are cached for future use.
Figure 5. BluePages reporting structure tab
Approaches to Bu ld ng H gh Performance Web Appl cat ons
Copyright ?© 2007, Idea Group Inc. Copying or distributing in print or electronic forms without written permission
of Idea Group Inc. is prohibited.
The LDAP Cache Controller servlet acts as the central management point. It delivers the
subsystem management views, and Web applications use a static method to access the Cache
Manager (Grand, 2002). The Cache Manager is the object that populates the cache and fails
over to LDAP as needed. It keeps track of metrics and performs any regular updates based
on the Data Refresh Scheduler.
As with the other cache subsystem, the LDAP cache has a management interface. The main
difference is the cache statistics view.
Pages:
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319