Changeset 1191

Timestamp:

07/03/17 14:34:21 (7 years ago)

Author:

rlacroix

Message:

Do not use the "min_buffer_size" parameter also as maximum event size.

Using the "min_buffer_size" as maximum event size caused the maximum number of bufferable events to be completely underestimated which could affect performance.

The new solution is not perfect either as it overestimates the maximum number of bufferable events in most cases. In theory this could cause deadlocks but in practice it should be mostly safe.

File:

• XIOS/trunk/src/node/context.cpp (modified) (1 diff)

XIOS/trunk/src/node/context.cpp

@@ -290 +290 @@
        if (it->second < minBufferSize) it->second = minBufferSize;
      }
-
-     // We consider that the minimum buffer size is also the minimum event size
-     ite = maxEventSize.end();
-     for (it = maxEventSize.begin(); it != ite; ++it)
-       if (it->second < minBufferSize) it->second = minBufferSize;
 
      client->setBufferSize(bufferSize, maxEventSize);