Re: Distributed testing and active threads over time

2018-09-05 Thread Philippe Mouawad
I don’ think it’s related. When did this issue appear ? Could you open a new mail thread and give more details on what you do and what you see in console and log ? Regards On Thursday, September 6, 2018, Jmeter Tea wrote: > Hello, > > It may not be related, but jmeterw isn't working on windows

Re: Distributed testing and active threads over time

2018-09-05 Thread Jmeter Tea
Hello, It may not be related, but jmeterw isn't working on windows it write to console : JMeter"" was unexpected at this time. FYI On Thu, Sep 6, 2018 at 12:35 AM, Philippe Mouawad < philippe.moua...@gmail.com> wrote: > Hello, > This has been implemented today within: > - https://bz.apache.org/

Re: Distributed testing and active threads over time

2018-09-05 Thread Philippe Mouawad
Hello, This has been implemented today within: - https://bz.apache.org/bugzilla/show_bug.cgi?id=62684 No additional CSV field was needed. It would be nice if you could review , test and give feedback. Regards On Fri, Jul 3, 2015 at 7:11 AM sebb wrote: > On 1 July 2015 at 21:59, Philippe Mouaw

Re: Distributed testing and active threads over time

2015-07-02 Thread sebb
On 1 July 2015 at 21:59, Philippe Mouawad wrote: > Good idea Andrei indeed. > > How do you see it: > >- Would we add a new field called : > - jmeter.save.saveservice.injid composed of host:port >- Or would we ad jmeter.save.saveservice.port and require users to set: > - jmeter.

Re: Distributed testing and active threads over time

2015-07-02 Thread Andrey Pokhilko
I would go with injid, single field. Andrey Pokhilko On 07/01/2015 11:59 PM, Philippe Mouawad wrote: > Good idea Andrei indeed. > > How do you see it: > >- Would we add a new field called : > - jmeter.save.saveservice.injid composed of host:port >- Or would we ad jmeter.save.saveser

Re: Distributed testing and active threads over time

2015-07-01 Thread Philippe Mouawad
Good idea Andrei indeed. How do you see it: - Would we add a new field called : - jmeter.save.saveservice.injid composed of host:port - Or would we ad jmeter.save.saveservice.port and require users to set: - jmeter.save.saveservice.hostname=true - jmeter.save.saveservice.p

Re: Distributed testing and active threads over time

2015-07-01 Thread sebb
On 1 July 2015 at 09:11, Andrey Pokhilko wrote: > Hi, > > Thanks for this initiative, I felt it painful for jp@gc, for > Loadosophia.org and for my new project Taurus. > > I would solve it with hostname+port pair in SampleResult, as it makes Using port is an excellent idea. Maybe as host:port as

Re: Distributed testing and active threads over time

2015-07-01 Thread Andrey Pokhilko
Hi, Thanks for this initiative, I felt it painful for jp@gc, for Loadosophia.org and for my new project Taurus. I would solve it with hostname+port pair in SampleResult, as it makes easier to map results to originating JMeter servers. Unique ID's would also solve it, but it will require additiona

Re: Distributed testing and active threads over time

2015-07-01 Thread sebb
On 1 July 2015 at 07:34, Philippe Mouawad wrote: > On Wednesday, July 1, 2015, sebb wrote: > >> On 30 June 2015 at 23:46, Philippe Mouawad > > wrote: >> > On Wednesday, July 1, 2015, sebb > >> wrote: >> > >> >> On 30 June 2015 at 22:16, Philippe Mouawad > >> >> > wrote: >> >> > Hello, >> >> > Wh

Re: Distributed testing and active threads over time

2015-06-30 Thread Philippe Mouawad
On Wednesday, July 1, 2015, sebb wrote: > On 30 June 2015 at 23:46, Philippe Mouawad > wrote: > > On Wednesday, July 1, 2015, sebb > > wrote: > > > >> On 30 June 2015 at 22:16, Philippe Mouawad > >> > wrote: > >> > Hello, > >> > When we do distributed testing and need afterwards to analyze > r

Re: Distributed testing and active threads over time

2015-06-30 Thread sebb
On 30 June 2015 at 23:46, Philippe Mouawad wrote: > On Wednesday, July 1, 2015, sebb wrote: > >> On 30 June 2015 at 22:16, Philippe Mouawad > > wrote: >> > Hello, >> > When we do distributed testing and need afterwards to analyze results, we >> > need to know how much threads were running at the

Re: Distributed testing and active threads over time

2015-06-30 Thread Philippe Mouawad
clarified last note On Wednesday, July 1, 2015, Philippe Mouawad wrote: > > > On Wednesday, July 1, 2015, sebb > wrote: > >> On 30 June 2015 at 22:16, Philippe Mouawad >> wrote: >> > Hello, >> > When we do distributed testing and need afterwards to analyze results, >> we >> > need to know how

Re: Distributed testing and active threads over time

2015-06-30 Thread Philippe Mouawad
On Wednesday, July 1, 2015, sebb wrote: > On 30 June 2015 at 22:16, Philippe Mouawad > wrote: > > Hello, > > When we do distributed testing and need afterwards to analyze results, we > > need to know how much threads were running at the some point in time by > > doing aggregation work, as illust

Re: Distributed testing and active threads over time

2015-06-30 Thread sebb
On 30 June 2015 at 22:16, Philippe Mouawad wrote: > Hello, > When we do distributed testing and need afterwards to analyze results, we > need to know how much threads were running at the some point in time by > doing aggregation work, as illustrated here: > > - http://jmeter-plugins.org/wiki/Activ

Distributed testing and active threads over time

2015-06-30 Thread Philippe Mouawad
Hello, When we do distributed testing and need afterwards to analyze results, we need to know how much threads were running at the some point in time by doing aggregation work, as illustrated here: - http://jmeter-plugins.org/wiki/ActiveThreadsOverTime/ I am just illustrating this need by this pa