Browse files


SVN Revision: 159
  • Loading branch information...
1 parent 61c7c58 commit a3a0628f0f7cb751b9105df3c786abee8ebd5b42 @nniclausse nniclausse committed Dec 19, 2003
Showing with 6 additions and 13 deletions.
  1. +6 −13 doc/Design.txt
@@ -6,6 +6,9 @@ The application is now split in two (see tsunami-inside.png for an overview):
** a single controller (tsunami_controller)
+ * ts_config_server (gen_server). Configuration server. Session's
+ definitions are kept by the config server.
* ts_mon (gen_server). Each client send reports of stats to this
server. Several types of messages are handled by ts_mon.
@@ -23,6 +26,9 @@ This application is simpler:
* ts_launcher (gen_fsm) launch simulated users.
+ * ts_session_cache (gen_server) cache the sessions's definition (ask
+ the config_server if it's not yet in the cache)
* 2 process per simultated client (ts_client, ts_client_rcv), under
the supervision of ts_clients_sup ( using simple_one_for_one )
@@ -42,19 +48,6 @@ Main modules:
b/ Each of these process will spawn a new process to handle
incoming data from the server (ts_client_rcv module).
- The total number of clients (NCLIENTS) can be changed in the
- config file. It represent the total number of clients that
- will be launched, and not the maximal simultaneous number of
- client.
- Warning: All the messages for a user session are computed by
- ts_launcher, just before spawning the user process (in a
- list). Therefore, if the number of messages is huge, it can
- takes A LOT of memory. If you want to do very long experiments,
- use a single 'dynamic' messages (see jabber_dynamic and
- Jabber.txt for an exemple), which will be send over and over by
- the user.
Important parameters for Jabber :
1/ chat messages size, in bytes (250 by default)

0 comments on commit a3a0628

Please sign in to comment.