after my stress test:
emski (unlocked) >>> info
{
"blockchain_head_block_num": 2941,
"blockchain_head_block_time": "20140625T060600",
"blockchain_head_block_time_rel": "45 seconds old",
"blockchain_confirmation_requirement": 303,
"blockchain_average_delegate_participation": 58.720930232558139,
"network_num_connections": 32,
"ntp_time": "20140625T060645.437978",
"ntp_error_seconds": 0.001075,
"wallet_unlocked_seconds_remaining": 999999548,
"wallet_next_block_production_time": "20140625T061000",
"wallet_seconds_until_next_block_production": 195,
"wallet_local_time": "20140625T060645",
"blockchain_random_seed": "1cf580c025e9d7d048da0307920d80b6d256c3e8",
"blockchain_shares": 199999133938247,
"network_num_connections_max": 200,
"network_protocol_version": 103,
"wallet_open": true,
"wallet_unlocked_until": "19100126T011737",
"wallet_version": 100
}
--- in sync with p2p network
emski (unlocked) >>> blockchain_list_forks
[
1842,
2577,
2631,
2938,
2940
]
--- there are now 33 active connections to the p2p network
--- in sync with p2p network
emski (unlocked) >>> about
{
"bitshares_toolkit_revision": "c0a8c268cd65dd7a7e4a7af0ef6f5c6c1ef763f8",
"bitshares_toolkit_revision_age": "32 minutes ago",
"fc_revision": "87a93940d046cc6715b67d9380dd280c27bdd867",
"fc_revision_age": "10 hours ago",
"compile_date": "compiled on Jun 25 2014 at 08:57:10"
}
The client seems to be responsive now.