Hi Lim. This sounds like an excellent idea. I also feel that this part is missing from JMeter. I have a few comments: 1. You should consider writing a plugin which can maybe be more simple to start with. 2. Smartphone will be a small challenge compared to real browsers. Once that is solve, smartphones implementation will be easy. 3. The tool I know that can simulate (automate) a browser is Selenium. Yet, it looks like a challenge (probably unlikely) to implement it into JMeter.
As I mentioned it sounds great and required. Alon. http://blazemeter.com/ On Sat, Apr 21, 2012 at 2:07 PM, Cheen-Pin Lim <[email protected]>wrote: > Hi, > > The tools mentioned help a great deal, however they generally look at it > from a single browser to a single server scenario. Once you have more load > applied to the servers/services different characteristics tend to emerge, > which is why I was thinking that the use of JMeter would be useful. > > Furthermore, if our primary audience is hitting the site using a browser, > then would it not make sense to use the same tool to simulate the load? > > Just my thoughts. > > regards, > CP > > On 21 April 2012 17:26, chaitanya bhatt <[email protected]> wrote: > > > Pleanty of awesome tools are already available for free to meet your > goals. > > > > Free: > > https://developers.google.com/pagespeed/ > > http://yslow.org/ > > > > Free or Premium: > > http://ajax.dynatrace.com/ajax/en/content/c-speed-page-load.aspx > > > > > > Selenium has a webdriver which you can plan on extending - if you will. > > IMHO Jmeter is not the right platform for this. > > Thanks > > Chaitnaya M Bhatt > > http://www.performancecompetence.com > > On Fri, Apr 20, 2012 at 11:55 PM, Cheen-Pin Lim <[email protected] > > >wrote: > > > > > Hi, > > > > > > After looking at the current HTTP Sampler, I would like to propose a > > > WebDriver based implementation. The problem is that with a lot of > modern > > > websites using AJAX, advanced CSS3 (transitions/transforms) to do the > > > rendering, the performance problem may not be 'visible' to the standard > > > HTTP Sampler. The idea is that if we could use JMeter to control a > > browser > > > and collect the time it takes to render each 'page' it would give the > > users > > > an understanding of how long a page would take to render. > > > > > > Some of the high level goals are as follows: > > > > > > 1. Allow any WebDriver supported browser to be used to perform the > > > Sampling. > > > 2. Provide a BeanShell/BSF style pane where the user can script the > > > behaviour of WebDriver. > > > > > > I've got a very basic implementation working here: > > > https://github.com/cplim/JMeter - you'll have to switch to the > > 'webmeter' > > > branch to see the changes. There are limitations with this proof of > > > concept, mainly: > > > > > > 1. It only creates Firefox instances > > > 2. I've only provided Javascript lang support using BSF. > > > > > > Some outstanding questions: > > > > > > 1. How to support Phone (Android/iOS) based WebDriver, as these seem > to > > > expect to only connect to a single phone. > > > > > > I would be happy to contribute the changes back to JMeter. Can I get > > some > > > feedback on this proposal, and what I need to do to contribute my > changes > > > back to the main JMeter codebase? > > > > > > regards, > > > CP Lim > > > > > >
