Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/tempo-vulture: share rand.Rand instance across multiple searches #1763

Merged
merged 3 commits into from
Oct 5, 2022

Commits on Sep 27, 2022

  1. cmd/tempo-vulture: share rand.Rand instance across multiple searches

    grafana#1760 noted that creating a new rand.Rand every time a
    random number is generated causes a poor distrubution of the search
    space, where numbers appear 7x more frequently than they do when using a
    shared rand.Rand instance.
    
    This is demonstrated using the following Go playground link: https://go.dev/play/p/EkhINRfOO5p
    
    This commit changes Vulture to use a shared rand.Rand instance instead
    of creating a new one each time a search or read is performed.
    rfratto committed Sep 27, 2022
    Configuration menu
    Copy the full SHA
    6310e59 View commit details
    Browse the repository at this point in the history
  2. update CHANGELOG

    rfratto committed Sep 27, 2022
    Configuration menu
    Copy the full SHA
    03402bf View commit details
    Browse the repository at this point in the history

Commits on Oct 5, 2022

  1. Configuration menu
    Copy the full SHA
    f535a97 View commit details
    Browse the repository at this point in the history