You probably already know this, but just in case. In terms of performance testing an application that uses large XML files, it will be limited by bandwidth.
100mbit has max of 10Mbyte/second 10Mb/concurrent request/message = max throughput per second Using the 50Mb file, this means a single request will take atleast 5 seconds to transfer. Realistically, if this is going over the internet, it's going to be double that 10 seconds per message. That roughly translates to 6 messages/minute for a single user. Once you start increasing the concurrent users, you can pretty much divide 6 per minute/users to get the theoritical max throughput. Considering the messages are soap, the actual throughput for a single user with 50Mb messages is going to be less than 3/minute. I can't stress enough that performance testing with large XML files is really testing the bandwidth and XML parser. the overall application processing time is such a small percent, that it really doesn't even matter. hope that's useful. peter On 12/5/05, Brudermann Roger <[EMAIL PROTECTED]> wrote: > > Dear JMeter Community > > We have the need to do performance testing with with huge SOAP and JMS > messages (e.g. 50MB). Instead of pasting these messages in a text box of > an > appropriate sampler, we had the idea to write an own sampler which reads > the > messages as data streams directly from the file system. So far so good. > > The problem is that we need to use pre processor variables (counters) to > customize the messages. We noticed that counter value replacing does not > take place and we think this is due to the fact that the messages are not > stored in a sampler property. Does somebody have an idea how we could > implement some "on the fly value replacing" while reading the message > stream > from the file system (e.g. line by line)? > > Any help is greatly appreciated! Thanks! > > Regards, > Roger Brudermann > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
