github.com/leonlxy/hyperledger@v1.0.0-alpha.0.20170427033203-34922035d248/docs/source/FAQ/usage_FAQ.rst (about)

     1  Usage
     2  -----
     3  
     4  * What are the expected performance figures for the fabric?
     5  
     6  The performance of any chain network depends on several factors: proximity
     7  of the validating nodes, number of validators, encryption method,
     8  transaction message size, security level set, business logic running,
     9  and the consensus algorithm deployed, among others.
    10  
    11  The current performance goal for the fabric is to achieve 100,000
    12  transactions per second in a standard production environment of about 15
    13  validating nodes running in close proximity. The team is committed to
    14  continuously improving the performance and the scalability of the
    15  system.
    16  
    17  * Do I have to own a validating node to transact on a chain
    18  network?
    19  
    20  No. You can still transact on a chain network by owning a
    21  non-validating node (NV-node).
    22  
    23  Although transactions initiated by NV-nodes will eventually be forwarded
    24  to their validating peers for consensus processing, NV-nodes establish
    25  their own connections to the membership service module and can therefore
    26  package transactions independently. This allows NV-node owners to
    27  independently register and manage certificates, a powerful feature that
    28  empowers NV-node owners to create custom-built applications for their
    29  clients while managing their client certificates.
    30  
    31  In addition, NV-nodes retain full copies of the ledger, enabling local
    32  queries of the ledger data.
    33  
    34  * What does the error string "state may be inconsistent, cannot
    35  query" as a query result mean?
    36  
    37  Sometimes, a validating peer will be out
    38  of sync with the rest of the network. Although determining this
    39  condition is not always possible, validating peers make a best effort
    40  determination to detect it, and internally mark themselves as out of
    41  date.
    42  
    43  When under this condition, rather than reply with out of date or
    44  potentially incorrect data, the peer will reply to chaincode queries
    45  with the error string "state may be inconsistent, cannot query".
    46  
    47  In the future, more sophisticated reporting mechanisms may be introduced
    48  such as returning the stale value and a flag that the value is stale.