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 service-threads and transaction-queues should match vm.num_cpus #354

Closed
cmccoy opened this issue Jun 29, 2015 · 3 comments
Closed
Assignees

Comments

@cmccoy
Copy link
Contributor

cmccoy commented Jun 29, 2015

These parameters are recommended to match the number of cores per http://www.aerospike.com/docs/reference/configuration/, currently they are fixed at 4.

@voellm
Copy link
Contributor

voellm commented Jun 29, 2015

+1 to fix this. We should follow the [default] recommendations. Any idea
why Aerospike does not default to this behavior?

On Mon, Jun 29, 2015 at 3:21 PM, Connor McCoy notifications@github.com
wrote:

These parameters are recommended to match the number of cores per
http://www.aerospike.com/docs/reference/configuration/, currently they
are fixed at 4.


Reply to this email directly or view it on GitHub
#354.

Anthony F. Voellm (aka Tony)
Google Voice: (650) 516-7382
https://www.google.com/voice/b/0?pli=1#phones
Blog: http://perfguy.blogspot.com/
Benchmark like a pro... PerfKitBenchmarker
https://github.com/GoogleCloudPlatform/PerfKitBenchmarker

@cmccoy
Copy link
Contributor Author

cmccoy commented Jul 1, 2015

I'm not sure, but it's hardly the only product where recommended values are in the docs rather than automatically set. Opened #360 to address this.

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

Closes #354
@cmccoy
Copy link
Contributor Author

cmccoy commented Jul 1, 2015

Resolved by #360.

@cmccoy cmccoy closed this as completed Jul 1, 2015
klausw added a commit that referenced this issue 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 issue Jul 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants