From 6ead5f6614b2acc104c4b550f163b45467aefd3e Mon Sep 17 00:00:00 2001
From: Jan Soukal <soukal@ics.muni.cz>
Date: Wed, 22 Aug 2012 16:49:00 +0200
Subject: [PATCH] doplneno vysvetleni MAX_RCV_EVENTS_LIMIT
---
src/warden-client/doc/CHANGELOG | 3 +++
src/warden-client/doc/README | 11 +++++++++++
2 files changed, 14 insertions(+)
diff --git a/src/warden-client/doc/CHANGELOG b/src/warden-client/doc/CHANGELOG
index a2fdab2..ee2d0d2 100644
--- a/src/warden-client/doc/CHANGELOG
+++ b/src/warden-client/doc/CHANGELOG
@@ -1,6 +1,9 @@
2012-00-00 v.2.1 stable version
-------------------------------
- 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
diff --git a/src/warden-client/doc/README b/src/warden-client/doc/README
index 2000239..cba389a 100644
--- a/src/warden-client/doc/README
+++ b/src/warden-client/doc/README
@@ -210,6 +210,17 @@ F. Configuration
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
--
GitLab