Query: kumostat
OS: debian
Section: 1
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
KUMOSTAT(1) General Commands Manual KUMOSTAT(1)NAMEkumostat - get kumofs statusSYNOPSISkumostat server-address[:port=19800] command kumostat -m manager-address[:port=19700] commandDESCRIPTIONGet status from Server node.COMMANDSpid get pid of server process uptime get uptime time get UNIX time version get version cmd_get get total number of processed get requests cmd_set get total number of processed set requests cmd_delete get total number of processed delete requests items get number of stored items rhs get rhs (routing table for Get) whs get whs (routing table for Set/Delete) hscheck check if rhs == whs set_delay maximize throughput at the expense of latency unset_delay maximize throughput at the expense of latencyDELAY MODEIf the delay mode is enabled, req/sec throughput is maximized at the expense of latency. This mode actually disables TCP_NODELAY option of all sockets. The practice of this feature is as following: - run some scripts that watches load of the kumo-server. (see source code of kumotop) - if the load of kumo-server becomes high, enable delay mode by kumostat set_delay command. - if the load of kumo-server becomes low, disable delay mode by kumostat unset_delay command.EXAMPLE$ kumostat svr1 items $ kumotop -m mgr1 hscheckSEE ALSOkumo-server(1). kumostat July 2009 KUMOSTAT(1)
Related Man Pages |
---|
auphone(1) - debian |
kumo-manager(1) - debian |
kumo-gateway(1) - debian |
kumoctl(1) - debian |
kumostat(1) - debian |
Similar Topics in the Unix Linux Community |
---|
linux prog for server space, load etc |
Need help with this script..please..thks |
server load tracking |
tool to monitor throughput |
Total number of users logged in a server from uptime |