Dispatch_Max_Reqs_Xprt is settable attribute that affects stalling the ganesha server when the outstanding requests in the queue supersedes the set value. The default value is 512 and can take 1 to 2048. Ganesha unstalls the server when the queuing requests decreases to half of the value.
I learned about the attribute from the code but still I couldn't fully understand it. We are developing our own FSAL and what we are seeing now is stalling occurs occasionally when the requests is too much. And the server always wakes up in one second. And when the server stalls clients seems to stop sending requests somehow (does Ganesha back-pressures when it stalls?) We are considering setting high value on the attribute but we aren't sure what the pros and cons of setting high value on it. Intuitively, setting high value may lead to stalling much less often but may lead to OOM on the other hand. I think Ganesha doesn't expect itself stalls too often because the code says it unlikely. That's why we are thinking of setting high value on it. Do you think setting high value is a good idea for us? And what else do you have in mind to solve our problem? Akira ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
