Stefano Bagnara wrote:
It would be cool to have a performance/stress test that allow to test
common setups. A benchmark could measure memory used and time needed to
perform a given task.
yes, that would be excellent!
such tests could also be 'health tests' to 'certify' an intermediate or
release build. it is my impression that maybe releases are held up
because it's too hard to tell if 'everything is ok'.
when running tools like postal, rabid and smtpsink for some days i could
never easily tell if things went good or bad - oh, at least when the
server broke down, i could ;-)
what i would love to have would be:
* tester specifies the number of internal users and external users.
* test environment generates all internal users in the tested James server
* tester specifies, how much mails should be floating around every minute:
a. coming in from external users for internal users
b. from internal users to internal users
c. going out from internal users to external
(some users may have significant differences in inbound/outbound
traffic, or even mostly internal mail traffic)
* for each set a,b,c the tester defines avg + max message size
* for each set a,b,c the tester defines how much percent have
attachments, and what the max attachment size is
* tester specifies for incoming mail how much spam should be simulated,
every 'spam' mail is marked with a special header.
* tester specifies the start/endtime of the test
* test generates mail traffic according to the given profiles
* test monitors the server and samples all data and makes it accessible
to tester
does that sound reasonable?
bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
