Scalability and Logging

[Tommy]

I was wondering what the most number of tests can be expected out of a server quality machine is.

We are currently have 5,000 test runnning on a dual processor machine with SCSI RAID 5. Many of these tests run every two minutes. This adds up to a lot of tests quite quickly. It is working fine but the program is slow to respond sometimes although the CPU nor memory do not look overly stressed.

Is any one else running this amount of tests off a single server?

Also we are beginning to log to an SQL database. Does anyone have any experience logging to SQL?

tom

I LOVE THIS PROGRAM!

[KS-Soft]

5000/120 = 42 tests per second. This is above average but not too much.
However CPU/memory/network load depends on test methods and test settings, e.g. simple ping test uses less resources than Process test.
BTW: There is "Estimate load" dialog (menu View) that display information about each test method.

If you record information about every test result into ODBC, it may slowdown system. Try to set "Enable connection pooling" option, located on Misc page in the Options dialog

Regards
Alex

[Marcus]

We perform about 9000 tests (most every 10 minutes) and log to sql (on the same server).

What we see is that the gui is slowly responding when a lot of tests are running, but tests are performed ok.

Enabling connection pooling solved our problem with an insufficient memory message for odbc logging.