Bug #8128

Some facts take a LOOONNGGG time to run

Added by James Turnbull 11 months ago. Updated 12 days ago.

Status:Accepted Start date:06/28/2011
Priority:High Due date:
Assignee:- % Done:

0%

Category:library
Target version:-
Keywords: Affected Facter version:
Branch:
Votes: 1

Description

FOr example puppetversion – it can take 600-800 ms per run:

puppetversion: 825.72ms

This is because it requires ‘puppet’ and loads it before returning the version. It should be rewritten to not do this.

Other heavy facts:

lsbdistid: 136.45ms
operatingsystem: 137.29ms
lsbdistdescription: 131.18ms
lsbdistrelease: 135.20ms
lsbmajdistrelease: 135.72ms
puppetversion: 137.39ms
lsbrelease: 132.03ms
lsbdistcodename: 134.41ms

Related issues

blocked by Facter - Feature #4519: Facter should provide a convenient way to cache values Accepted 08/11/2010

History

Updated by James Turnbull 11 months ago

  • Subject changed from puppetversion fact takes a LOOONNGGG time to run to Some facts take a LOOONNGGG time to run

Updated by Brice Figureau 11 months ago

The lsb facts on debian (at least on lenny) are taking a looong time because sometimes lsb_release need to resort to run apt/dpkg to find the local debian version which in itself is slooow… Too bad when you can grab the very same info from /etc/lsb_release if it exists…

Updated by R.I. Pienaar 11 months ago

fwiw those times above were from redhat, i didnt get time yet to see why lsb_release is so slow on rhel

Updated by Adrien Thebo 7 months ago

  • Description updated (diff)

Updated by Adrien Thebo 7 months ago

  • Description updated (diff)

Updated by Nigel Kersten 7 months ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Nigel Kersten)

Updated by Ken Barber 6 months ago

  • Assignee set to Ken Barber
  • Target version set to 2.0.0

Updated by Ken Barber 6 months ago

  • Target version changed from 2.0.0 to 186

Updated by Adrien Thebo 5 months ago

Ken, can we just mark this a duplicate of the fact caching?

Updated by Ken Barber 5 months ago

Yeah not sure – Its a bit of a blanket ticket. Cache is just 1 solution I think, but other optimisations may be found.

Updated by Daniel Pittman 2 months ago

  • Target version deleted (186)

Updated by Ken Barber 12 days ago

  • Assignee deleted (Ken Barber)

Also available in: Atom PDF