Ok, I noticed that the server-client mode isn't effective. Then i will use a lot of clients in non-gui batch mode. How do you merge the results of all the clients?
-----Original Message----- From: BAZLEY, Sebastian [mailto:[EMAIL PROTECTED] Sent: Monday, March 08, 2004 10:50 AM To: 'JMeter Users List' Subject: RE: Threads in remote hosts All remote hosts are sent the same testplan with the same settings. The plan is not divided between the servers. Client-server mode is very much less efficient than running independently. I suggest you run each host in batch (non-GUI) mode and combine the results. Check the archives for this list - there was some discussion on this a month or so ago. S. -----Original Message----- From: Raphael Philipe Mendes da Silva [mailto:[EMAIL PROTECTED] Sent: 08 March 2004 13:22 To: Jmeter Users List (E-mail) Subject: Threads in remote hosts Hi, I will have use Jmeter to do requests in a web server. I`ve created a thread group, a http request and some listiners. I have machines with differents configurations then i can't use the same thread nunber in all of then, because the limitations of CPU and Memory. How the number of threads is shared beteew the remote hosts? This number can be configured for each remote host? If not, how it share the number of threads in each remote host? It simple put the same number seted in thread number in each machine or it divides the number between the remot hosts?? Reguards Raphael Philipe Mendes da Silva DSB - Diretoria de Solu��es em Billing CPqD Telecom & IT Solutions Tel.: +55 19 3705-6957 www.cpqd.com.br [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ___________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
