Hi. Since it''s my first time posting to this group, I''ll preface my question with the usual: Puppet is magic and has brought color and joy to my world. With that behind us, I''ve recently begun to play with the LDAPNodes capabilities and found that the ruby/ldap library used is unbearably slow. I''ve isolated it from Puppet itself by putting together a test script using ruby/ldap that simply searches for a particular DN and prints it out. Network communication happens in a matter of milliseconds (verified with tcpdump), but then we have a full 40-45 seconds before the client finally sends the TCPFIN and dumps the results to my console. A nearly identical script using net/ldap, however, is lightning fast. This is going from FreeBSD 7.2 to Windows 2003 ADS. Has anybody else experienced this issue? Is there a particular reason ruby/ldap was chosen over net/ldap? -Shawn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
S H wrote:> > Has anybody else experienced this issue? Is there a particular reason > ruby/ldap was chosen over net/ldap? >Is net/ldap still maintained or developed? Even so I think it''s because the ruby-ldap client is packaged for a variety of operating systems whilst I don''t believe net/ldap is? Luke can probably shed some light. Regards James -- Author of: * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux)
On Wed, Jun 24, 2009 at 5:26 PM, James Turnbull <james@lovedthanlost.net>wrote:> S H wrote: > > > > Has anybody else experienced this issue? Is there a particular reason > > ruby/ldap was chosen over net/ldap? > > > > Is net/ldap still maintained or developed? Even so I think it''s because > the ruby-ldap client is packaged for a variety of operating systems > whilst I don''t believe net/ldap is? > > Luke can probably shed some light. > > Regards > > JamesBoth seem to have been deserted by their official maintainers in August 2006, according to their sourceforge sites. net/ldap wasn''t packaged for FreeBSD, but it was available as a gem so that was pretty minor (for me). -Shawn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On 2009-Jun-24, at 5:11 PM, S H wrote:> With that behind us, I''ve recently begun to play with the LDAPNodes > capabilities and found that the ruby/ldap library used is unbearably > slow.I haven''t noticed any slowness, but I did see some errors from Puppet saying the node couldn''t be found, while the corresponding log on the LDAP server shows the results being returned. I assume this is a bug in ruby-ldap and not Puppet (and I haven''t seen it happen recently).> I''ve isolated it from Puppet itself by putting together a test > script using ruby/ldap that simply searches for a particular DN and > prints it out.If you want to send me this script, I can try it on one of my RHEL5 or Debian systems. This might help narrow down what the problem is. -- Rob McBroom <http://www.skurfer.com/> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Thu, Jun 25, 2009 at 11:33 AM, Rob McBroom <mailinglist0@skurfer.com>wrote:> > On 2009-Jun-24, at 5:11 PM, S H wrote: > > > With that behind us, I''ve recently begun to play with the LDAPNodes > > capabilities and found that the ruby/ldap library used is unbearably > > slow. > > I haven''t noticed any slowness, but I did see some errors from Puppet > saying the node couldn''t be found, while the corresponding log on the > LDAP server shows the results being returned. I assume this is a bug > in ruby-ldap and not Puppet (and I haven''t seen it happen recently). > > > I''ve isolated it from Puppet itself by putting together a test > > script using ruby/ldap that simply searches for a particular DN and > > prints it out. > > If you want to send me this script, I can try it on one of my RHEL5 or > Debian systems. This might help narrow down what the problem is. > > -- > Rob McBroom > <http://www.skurfer.com/>Thanks for the offer. I think I finally tracked this down to the virtual environment I was testing in since I can''t replicate it on my physical hardware. Sorry for the spam! -Shawn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---