luca-simonetti commented on issue #5044:
URL: https://github.com/apache/couchdb/issues/5044#issuecomment-2090514057

   no the database is not growing during the read operations (the actual 
platform is a QA environment where the only operation is the "mega read"). 
We're speaking of  100.000 reads.
   Also: right after the restart the whole thing gets back to normal (200ms) 
and starts degrade again in a couple of minutes.
   
   `_active_tasks` is empty (`[]`)
   I'm not sure what do you mean by our map/reduce since we're using the 
Hyperledger API to access the CouchDB
   
   I can show you the go code for the chaincode we does the reads though:
   
   ```go
   func (c *xxxxx) Token(ctx contractapi.TransactionContextInterface, tokenId 
string) (string, error) {
   
        token, err := GetTokenData(ctx, tokenId)
        if err != nil {
                return "", err
        }
   
        tokenxxxxx := xxxxxx
        iterator, err := 
ctx.GetStub().GetStateByPartialCompositeKey(PrefixTokenxxxxxx, 
[]string{tokenId})
        if err != nil {
                return "", fmt.Errorf("error creating asset chaincode: %v", err)
        }
        for iterator.HasNext() {
                queryResponse, err := iterator.Next()
                if err != nil {
                        return "", err
                }
                // Recupero il tokenId
                _, compositeKeyParts, err := 
ctx.GetStub().SplitCompositeKey(queryResponse.Key)
                if err != nil {
                        return "", err
                }
   
                /// OTHER CODE REDACTED BUT OF NO CONCERN
        }
        _ = iterator.Close()
        resultByte, err := json.Marshal(tokenWithxxxxxxx)
        return string(resultByte), nil
   }
   
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to