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.

Sign up for GitHub

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

Jump to bottom

Aerospike: Use vm.num_cpus where recommended. #360

Merged
merged 3 commits into from
Jul 1, 2015
Merged

Aerospike: Use vm.num_cpus where recommended. #360

merged 3 commits into from
Jul 1, 2015

Commits on Jul 1, 2015

  1. Use vm.num_cpus for aerospike service-threads, transaction-queues

    @cmccoy
    cmccoy committed Jul 1, 2015
    Configuration menu
    Copy the full SHA
    9357d7a View commit details
    Browse the repository at this point in the history

  2. Always render aerospike.conf 

    Switches on presence / absence of 'devices' to determine whether the
backend should be disk.
    @cmccoy
    cmccoy committed Jul 1, 2015
    Configuration menu
    Copy the full SHA
    5d4957b View commit details
    Browse the repository at this point in the history

  3. Keep rendered templates in the VM temporary directory 

    Aids debugging.
    @cmccoy
    cmccoy committed Jul 1, 2015
    Configuration menu
    Copy the full SHA
    0017d02 View commit details
    Browse the repository at this point in the history