Skip to content
This repository has been archived by the owner on Jan 21, 2021. It is now read-only.

Make pool size parameters configurable #5

Closed
fquinner opened this issue Sep 16, 2015 · 1 comment
Closed

Make pool size parameters configurable #5

fquinner opened this issue Sep 16, 2015 · 1 comment
Milestone

Comments

@fquinner
Copy link
Collaborator

Including number of nodes to allocate and the size of each node.

fquinner added a commit that referenced this issue Sep 19, 2015
@fquinner fquinner added this to the 1.0 milestone May 8, 2016
@fquinner
Copy link
Collaborator Author

fquinner commented Jun 2, 2016

commit e3c6343
Author: Frank Quinn fquinn.ni@gmail.com
Date: Thu Jun 2 21:41:48 2016 +0100

Added new configuration parameters for message pool and node sizes

I provided sample usage in the configuration:

mama.zmq.transport.sub.msg_pool_size=1024
mama.zmq.transport.sub.msg_node_size=4096

Pool size is in number of nodes and node size is in bytes. A larger
initial pool will mean fewer allocations if the subscriber is likely
to be placed under pressure.

@fquinner fquinner closed this as completed Jun 2, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant