Hey Matt,

Thanks: is "pillowfight" available as a command utility eg 

Name

cbc — Couchbase command line utility
Synopsis

*cbc help*

*cbc cat* [common options] [-r [*VALUE*]] *key*…

*cbc cp* [common options] [-p] [-r *NUMBER*] [-m *NUMBER*] [-j] *filename*…

*cbc create* [common options] [-f *FLAGS*] [-e *VALUE*] [-a] *key*

*cbc observe* [common options] *key*…

*cbc flush* [common options]

*cbc hash* [common options] [-f *FILENAME*] *key*…

*cbc lock* [common options] [-e *VALUE*] *key*…

*cbc unlock* [common options] *key* *cas*…

*cbc rm* [common options] *key*…

*cbc stats* [common options] [*stat group*]…

*cbc verify* [common options] *filename*…

*cbc version* [common options]

*cbc verbosity* [common options] *level*

*cbc view* [common options] [-c] [-d *DATA*] [-X *METHOD*] *query*

*cbc admin* [common options] [-c] [-d *DATA*] [-X *METHOD*] *query*

*cbc bucket-create* [common options] [-B *TYPE*] [-q *QUOTA*] [-a *AUTH*] 
[-s *PASSWORD*] [-r *NUMBER*] [-p *PORT*] *bucketname*…

*cbc bucket-delete* [common options] *bucket*…

*cbc bucket-flush* [common options] *bucket*…

*cbc pillowfight* [-?] [-h *HOST*] [-b *BUCKET*] [-u *USER*] [-P *PASSWORD*] 
[-T] [-i *ITERATIONS*] [-I *ITEMS*] [-p *PREFIX*] [-t *THREADS*] [-Q 
*INSTANCES*] [-l] [-s *SEED*] [-r *RATIO*] [-m *MIN*] [-M *MAX*] [-d]


but when I try to run this I don't see the pillowfight option


C:\Program Files\Couchbase\Server\bin>couchbase-cli.exe -help

usage: couchbase-cli COMMAND CLUSTER [OPTIONS]


CLUSTER is --cluster=HOST[:PORT] or -c HOST[:PORT]


COMMANDs include

  server-list           list all servers in a cluster

  server-info           show details on one server

  server-add            add one or more servers to the cluster

  server-readd          readd a server that was failed over

  rebalance             start a cluster rebalancing

  rebalance-stop        stop current cluster rebalancing

  rebalance-status      show status of current cluster rebalancing

  failover              failover one or more servers

  cluster-init          set the username,password and port of the cluster

  cluster-edit          modify cluster settings

  node-init             set node specific parameters

  bucket-list           list all buckets in a cluster

  bucket-create         add a new bucket to the cluster

  bucket-edit           modify an existing bucket

  bucket-delete         delete an existing bucket

  bucket-flush          flush all data from disk for a given bucket

  bucket-compact        compact database and index data

  setting-compaction    set auto compaction settings

  setting-notification  set notification settings

  setting-alert         set email alert settings

  setting-autofailover  set auto failover settings

  setting-xdcr          set xdcr related settings

  user-manage           manage read only user

  xdcr-setup            set up XDCR connection

  xdcr-replicate        xdcr operations

  help                  show longer usage/help and examples


On Wednesday, January 29, 2014 7:23:38 PM UTC, Matt Ingenthron wrote:
>
> Hi Paul,
>
> How is your bucket set up?
>
> Note that by default, you'll have replication set to 1, so when you go 
> from one node to two nodes, you actually increase the reliability and thus 
> the work a bit without actually increasing net capacity.
>
> It may also be helpful if you give us a sense of the system under test and 
> the numbers you're seeing.  Note that there is a package distributed with 
> libcouchbase <http://www.couchbase.com/communities/c/getting-started>that 
> includes a workload generator named pillowfight.  There's also a Java 
> workload generator named RoadRunner <https://github.com/daschl/RoadRunner>
> .
>
> Thanks,
>
> Matt
>
> From: asdf9898 <[email protected] <javascript:>>
> Reply-To: "[email protected] <javascript:>" <
> [email protected] <javascript:>>
> Date: Thursday, January 30, 2014 4:00 AM
> To: "[email protected] <javascript:>" 
> <[email protected]<javascript:>
> >
> Subject: couchbase scale out performance
>
> Hello
>
> I am new to nosql in general and would like some advice on couchbase and 
> other similar technologies.
>
> I have done some performance testing of a number of technologies and find 
> the same results with each.
>
> When I do x inserts on a single node I get better performance than when I 
> add a second node.
>
> Read-performance is much better than insert performance but again a single 
> node performs better than 2 nodes.
>
> I then thought that if I add the URIs in the buildConnection
>
>                 URI server = new URI(addresses);
>                 ArrayList<URI> serverList = new ArrayList<URI>();
>                 serverList.add(server);
>                 CouchbaseClient client = new CouchbaseClient(
>                         serverList, "default", "");
>
> In other words by explicitly telling the client about the second node it 
> should cause double performance but sadly I just got maybe an extra 10%
>
> I then thought if I double the number of client threads because I now have 
> two servers to target it would double performance but again no: just a 
> slight increase.
>
> So in summary : would adding an extra node cause an increase or decrease 
> in throughput (both reading and inserts) ? 
>
> And I am getting the same behaviour using other well known nosql 
> technologies too.
>
> Many thanks in advance.
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Couchbase" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
> -- 
> Matt Ingenthron
> Couchbase, Inc.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Couchbase" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to