Agreed. ==
We had a similar requirement (private protocol over TCP/IP, persistent connection). This was implemented using a Java controller add-in. This turned out to be slightly awkward to use, so I've now started recoding it as a TCP Controller - derived from the the FTP Controller, which seemed the closest (and one of the simplest). The intention is for the TCP controller to handle connection setup and closedown, providing common services to a (selectable) protocol add-in that handles the content. It's not quite ready for use, but I hope to have something working in a day or two. [Let me know if you would like an copy...] == As to the architecture, as I understand it JMeter creates a separate instance of each sampler test element for each thread. This means that samplers don't have to worry much about synchronisation, and works well for connect/sample/disconnect protocols, but is not ideal for persistent connections. In our case, we want to use a separate persistent connection for each thread. The connection is to be used by one or more samplers in the same thread. It sounds like your needs are similar? This can be achieved using thread-local storage or perhaps JMeter thread variables. == As to adding a Timer, I would suggest (starting by) using the existing delay and throughput controllers. You can always use a function variable to control them. The controller could save the desired timeout in the variable if required. == Hope this helps. S. -----Original Message----- From: peter lin [mailto:[EMAIL PROTECTED] Sent: 22 September 2003 02:48 To: JMeter Developers List Subject: Re: Design question the first step is to write a sampler using your custom driver. You should be able to test it out with the default controllers, then you can work on your own custom controller. peter Patrick LeBoutillier <[EMAIL PROTECTED]> wrote: Hi, I'm new to JMeter and want to use it to do performance testing on an application we have that uses a proprietary protocol. Also, the application uses a persistent connection. Users typically connect to the server in the morning and disconnect in late afternoon. I have ASCII files that contain daily 'sessions', i.e. every request sent for a specific user, followed by the idle time until the next request. I want to replay these 'sessions' (possibly at a faster rate) in order to to load testing on the application server My plan is to write a custom Controler that will connect to the server at startup and then open one of the session files and loop through the request. I also need a custom Timer that will pause for the length of the idle time until the next request. My questions are: - Is this the right way to tackle this problem? - If so, is there a way to get the Timer to ask the Controler for the next amount of idle time? (I'm a bit confused as to how the architecture goes...) Thanks, Patrick ---------------------------------- | Patrick LeBoutillier | [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
