Rundeck integration very slow

I'm running foreman 1.5.1 on RHEL 6 and I have an instance of rundeck
pulling node data from foreman. I have about 110 hosts in foreman. When I
hit the URI /hosts?rundeck=true&format=yaml, it takes about 5 seconds to
complete the request. I have caching enabled on the rundeck side (I can
see it sending the If-None-Match header and receiving a 304 Not Modified),
and I'm running foreman_memcached. Does anyone have any suggestions on how
I can speed this up?

> I'm running foreman 1.5.1 on RHEL 6 and I have an instance of rundeck
> pulling node data from foreman. I have about 110 hosts in foreman. When I
> hit the URI /hosts?rundeck=true&format=yaml, it takes about 5 seconds to
> complete the request. I have caching enabled on the rundeck side (I can
> see it sending the If-None-Match header and receiving a 304 Not Modified),
> and I'm running foreman_memcached. Does anyone have any suggestions on how
> I can speed this up?
>

I would suggest to provide foreman logs, ideally with debug
enabled…rundeck code has been left alone for a very long time :slight_smile:

Ohad

··· On Thu, Aug 21, 2014 at 10:16 PM, Andy Bohne wrote:


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

I've uploaded a debug level log
to https://gist.github.com/abohne/4795529234420ecbbb55

This was captured after blocking all puppet connections using iptables, and
restarting httpd

··· On Thursday, August 21, 2014 4:00:13 PM UTC-4, ohad wrote: > > > > > On Thu, Aug 21, 2014 at 10:16 PM, Andy Bohne > wrote: > >> I'm running foreman 1.5.1 on RHEL 6 and I have an instance of rundeck >> pulling node data from foreman. I have about 110 hosts in foreman. When I >> hit the URI /hosts?rundeck=true&format=yaml, it takes about 5 seconds to >> complete the request. I have caching enabled on the rundeck side (I can >> see it sending the If-None-Match header and receiving a 304 Not Modified), >> and I'm running foreman_memcached. Does anyone have any suggestions on how >> I can speed this up? >> > > I would suggest to provide foreman logs, ideally with debug > enabled...rundeck code has been left alone for a very long time :) > > Ohad > > >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > >

Did anyone have a chance to look at the debug log?

··· On Thursday, August 21, 2014 5:38:28 PM UTC-4, Andy Bohne wrote: > > I've uploaded a debug level log to > https://gist.github.com/abohne/4795529234420ecbbb55 > > This was captured after blocking all puppet connections using iptables, > and restarting httpd > > On Thursday, August 21, 2014 4:00:13 PM UTC-4, ohad wrote: >> >> >> >> >> On Thu, Aug 21, 2014 at 10:16 PM, Andy Bohne >> wrote: >> >>> I'm running foreman 1.5.1 on RHEL 6 and I have an instance of rundeck >>> pulling node data from foreman. I have about 110 hosts in foreman. When I >>> hit the URI /hosts?rundeck=true&format=yaml, it takes about 5 seconds to >>> complete the request. I have caching enabled on the rundeck side (I can >>> see it sending the If-None-Match header and receiving a 304 Not Modified), >>> and I'm running foreman_memcached. Does anyone have any suggestions on how >>> I can speed this up? >>> >> >> I would suggest to provide foreman logs, ideally with debug >> enabled...rundeck code has been left alone for a very long time :) >> >> Ohad >> >> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Foreman users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to foreman-user...@googlegroups.com. >>> To post to this group, send email to forema...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >>