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

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

Conversation

cmccoy
Copy link
Contributor

@cmccoy cmccoy commented Jul 1, 2015

Use vm.num_cpus for Aerospike configurations service-threads, transaction-queues.
This is the recommended value per the documentation.

See #354.

Also modifies vm_util.NamedTemporaryFile to optionally delete the created
file (rather than always deleting it), so that rendered templates can be saved
to the run temp dir for debugging. I can separate that out if preferred.

Switches on presence / absence of 'devices' to determine whether the
backend should be disk.
@cmccoy
Copy link
Contributor Author

cmccoy commented Jul 1, 2015

test this please.

@ehankland
Copy link
Contributor

LGTM

cmccoy added a commit that referenced this pull request Jul 1, 2015
Aerospike: Use vm.num_cpus where recommended.

Closes #354
@cmccoy cmccoy merged commit 39e98e8 into GoogleCloudPlatform:dev Jul 1, 2015
@cmccoy cmccoy deleted the aerospike-use-num-cpus branch July 1, 2015 17:02
@voellm
Copy link
Contributor

voellm commented Jul 1, 2015

It looks like we are missing one thing with this change and that is the ability to override the num_cpus to change the default behavior back to use just 4 CPUs.

This means there will be some surprises in results and we should message it clearly in the coming release. It was wrong in the first place so I dont think we should add yet another flag to preserve the behavior that was there.

We follow the defaults and when we find an error we should fix it.

klausw added a commit that referenced this pull request Jul 9, 2015
Release 0.18.0.

(See also #369
which includes this change log with clickable GH-* links.)

* New features:
  * Support OpenStack as cloud provider (GH-305, GH-353, thanks @kivio and
    @mateusz-blaszkowski)
  * Support Rackspace as cloud provider (GH-336, thanks @meteorfox and @jrperritt)
  * Add support for ContainerizedVM using docker exec (GH-333, thanks @gablg1)
  * Windows guest VM support on Static VM (GH-350), Azure (GH-349, GH-374), AWS
    (GH-347), and GCE (GH-338)
  * Add NTttcp Windows networking benchmark (GH-348)

* Enhancements:
  * Support using proxies in VMs (GH-339, GH-337, thanks @kivio)
  * Enable optional migration on GCE (GH-343)
  * Execute long running commands via a remote agent (GH-310)
  * Add resource creation/deletion times to logs (GH-316)

* Bugfixes and maintenance updates:
  * Update PKB to work with Azure version 0.9.3 (GH-312)
  * Fix AWS CLI usage on Windows host (GH-313)
  * Auto-fetch AMI IDs for AWS images (GH-364)
  * Fix publisher missing info for default image and machine type (GH-357)
  * Fix 'no attribute pkb_thread_log_context' error for sub-thread logs (GH-322)

* Benchmark-specific changes:
  * aerospike: config/flag handling bugfixes (GH-367, GH-360, GH-354)
  * cassandra_ycsb: move num_vms prerequisite check
  * fio: add latency percentiles for results (GH-344)
  * hadoop_terasort: Fix bad SSH option (GH-328)
  * iperf: add lower bounds to arguments (GH-314)
  * iperf: add timeout to parallel benchmark runs to handle iperf hangs (GH-375)
  * netperf: Support confidence intervals, increase test length, report stddev
    (GH-317, GH-306)
  * ycsb: Drop unaggregatable results from samples (GH-324)

* Development and testing:
  * **Breaking Change** Automated testing now uses `tox` (GH-330)
  * Refactored hook scripts, including new opt-in pre-push hook (GH-363)
  * Use travis for CI testing (GH-340)
  * Speed up tests using timeouts (GH-299)

* Internals:
  * Move defaults from benchmark_spec to VM classes, move network instantiation
    out of benchmark spec (GH-342)
  * Add event hook support (GH-315)
  * Refactor VM classes (GH-321)
@klausw klausw mentioned this pull request Jul 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants