Re: SampleSender modes

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: SampleSender modes

Philippe Mouawad
Hi,
Any feedback on this ?

Regards

On Thu, Oct 12, 2017 at 4:35 PM, Philippe Mouawad <
[hidden email]> wrote:

> Hello,
> We have currently 10 modes and I believe at least 3 of them are useless:
>
> - DiskStore : Probably overwhelms disks / IO and the fact that results are
> sent at end will probably induce an important network traffic and time to
> get the results. Any issue in network or injector will loose results.
> - StrippedDiskStore : The fact that results are sent at end will probably
> induce an important network traffic and time to get the results. Any issue
> in network or injector will loose results.
> - Hold : holds results in memory which makes it useless IMO
>
> I propose to drop them.
> If anybody uses them, let him speak now or remain silent until the end of
> times :-)
>
>
> Regards
> Philippe
>



--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie

UBIK LOAD PACK Web Site <http://www.ubikloadpack.com/>

UBIK LOAD PACK on TWITTER <https://twitter.com/ubikloadpack>
Philippe M.
@philmdot
http://ubikloadpack.com
Reply | Threaded
Open this post in threaded view
|

Re: SampleSender modes

Emilian Bold
These "modes" are actually "services". When you configure the mode in
some .properties file you basically pick which service gets used.

We should not have a SampleSenderFactory that does an `if` on modes,
we should have a more generic mechanism where any such sample sender
implementation might exist.

When looking at things like this, I don't see how a mode existing or
not bothers anybody. Why shouldn't I be able to use a RAMdisk and use
the 'DiskStore' "mode"? Did you know Google Cloud has instances with
hundreds of GB of RAM? Rather cheap too if you only needs if a few
hours!

> Any issue in network or injector will loose results.

Any reason JMeter server has to be so brittle?

Instead of dropping modes, I'd say we focus on doing a sample sender
infrastructure where bi-directional connections aren't mandatory (drop
Java RMI) and allow some network hiccups (have some buffered message
queues or something).

My 2c.


--emi


On Mon, Oct 23, 2017 at 9:19 PM, Philippe Mouawad
<[hidden email]> wrote:

> Hi,
> Any feedback on this ?
>
> Regards
>
> On Thu, Oct 12, 2017 at 4:35 PM, Philippe Mouawad <
> [hidden email]> wrote:
>
>> Hello,
>> We have currently 10 modes and I believe at least 3 of them are useless:
>>
>> - DiskStore : Probably overwhelms disks / IO and the fact that results are
>> sent at end will probably induce an important network traffic and time to
>> get the results. Any issue in network or injector will loose results.
>> - StrippedDiskStore : The fact that results are sent at end will probably
>> induce an important network traffic and time to get the results. Any issue
>> in network or injector will loose results.
>> - Hold : holds results in memory which makes it useless IMO
>>
>> I propose to drop them.
>> If anybody uses them, let him speak now or remain silent until the end of
>> times :-)
>>
>>
>> Regards
>> Philippe
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
> Ubik-Ingénierie
>
> UBIK LOAD PACK Web Site <http://www.ubikloadpack.com/>
>
> UBIK LOAD PACK on TWITTER <https://twitter.com/ubikloadpack>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]