Uploaded image for project: 'Qpid Dispatch'
  1. Qpid Dispatch
  2. DISPATCH-11

Remove all the Dispatch tunables; we have no idea if they're important

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 0.1
    • Backlog
    • None
    • None

    Description

      A car has a simple interface: steering, gear selection, lights,
      wipers. Those things are important to drivers.

      A car also has another interface, for car mechanics: valve timing,
      fuel-air mix, and more stuff I'm pretending I know about.

      Dispatch's config is currently confronting drivers with things only
      car mechanics should have to care about: "worker-threads",
      "hello-interval", "hello-max-age", "ra-interval",
      "remote-ls-max-age", "mobile-addr-max-age".

      That's the wrong bias. It's much to be preferred that we, the
      people developing the software, discover ways to provide good
      defaults that don't require tunables. Then, only when we face a
      particular need and no way to handle it seamlessly, should we
      consider exposing config for it.

      Build it for drivers, not car mechanics.

      http://stackoverflow.com/questions/150355/programmatically-find-the-number-of-cores-on-a-machine

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jross Justin Ross
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: