Sounds like your process is spending a lot of time in blocked state (real - user - sys). Check your os subsystems, maybe your machine is bogged down by other work.
FWIW, my time in an idle system is about 2 seconds but can go up to ~13 seconds on a busy system with 70% cpu utilized. No difference between 1 and 3 node setups. All the best, [image: datastax_logo.png] <http://www.datastax.com/> Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] <https://www.linkedin.com/company/datastax> [image: facebook.png] <https://www.facebook.com/datastax> [image: twitter.png] <https://twitter.com/datastax> [image: g+.png] <https://plus.google.com/+Datastax/about> <http://feeds.feedburner.com/datastax> <http://goog_410786983> <http://www.datastax.com/gartner-magic-quadrant-odbms> DataStax is the fastest, most scalable distributed database technology, delivering Apache Cassandra to the world’s most innovative enterprises. Datastax is built to be agile, always-on, and predictably scalable to any size. With more than 500 customers in 45 countries, DataStax is the database technology and transactional backbone of choice for the worlds most innovative companies such as Netflix, Adobe, Intuit, and eBay. On Wed, Jun 22, 2016 at 9:03 AM, Bhuvan Rawal <bhu1ra...@gmail.com> wrote: > Hi, > > We have been facing slowness in getting response from nodetool for any of > its subcommand. On the same version on AWS it responds really fast but on > local 1 node machine or local DC cluster it performs very slow. > > On Local DC : > *$ time nodetool version* > ReleaseVersion: 3.0.3 > > real 0m*17.582s* > user 0m2.334s > sys 0m0.470s > > On AWS: > *$ time nodetool version* > ReleaseVersion: 3.0.3 > > real 0m*1.084s* > user 0m1.772s > sys 0m0.363s > > Any way by which its speed can be increased? > > Thanks & Regards, > Bhuvan >
