Skip to content
Snippets Groups Projects
Commit 6ead5f66 authored by Jan Soukal's avatar Jan Soukal
Browse files

doplneno vysvetleni MAX_RCV_EVENTS_LIMIT

parent 1a7634b1
No related branches found
No related tags found
No related merge requests found
2012-00-00 v.2.1 stable version 2012-00-00 v.2.1 stable version
------------------------------- -------------------------------
- receiving of all types of messages now supported - receiving of all types of messages now supported
- added support for batch processing
- maximum number of events received ($MAX_RCV_EVENTS_LIMIT) in one batch can
be set in etc/warden-client.conf. Default is 6000.
2012-07-27 v.2.0 stable version and bugfix release of warden-client-2.0.0-beta 2012-07-27 v.2.0 stable version and bugfix release of warden-client-2.0.0-beta
......
...@@ -210,6 +210,17 @@ F. Configuration ...@@ -210,6 +210,17 @@ F. Configuration
e.g. '/etc/ssl/certs/tcs-ca-bundle.pem' e.g. '/etc/ssl/certs/tcs-ca-bundle.pem'
Client receives events in batches. Maximum number of events received in one
batch can is set in MAX_RCV_EVENTS_LIMIT. Note that this option only
affects clients that receives events from the Warden server (e.g., uses
lib/WardenClientReceive.pm module).
MAX_RCV_EVENTS_LIMIT - maximum number of events in one batch
- default set to 6000, which generates app. 250 MB
of memory consumption.
- only affects "receiving" clients
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
G. Registration G. Registration
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment