;>>>>>>>>>>> — apache_ignite_root_folder
>>>>>>>>>>>>>>>>> — examples
>>>>>>>>>>>>>>>>> — bin
>>>>>>>>>>>>>>>>> —
ll the use case you’ve met
>>>> previously?
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>> —
>>>> >>>>>>>>>>>> Denis
>>>> >>>>>&
;>>>>>>>>>
>>> >>>>>>>>>>>>> Yardstick requires own scripts/configurations (/bin,
>>> /config,
>>> >>>>> /libs)
>>> >>>>>>>>>> and
>>> >>>>>>>>>&g
;>>>>>> Also
>> >>>>>>>>>> it
>> >>>>>>>>>>>>> may break the current user understanding of "libs/optional"
>> >>>>>>>> directory
>> >>>>>>>>>> as
>
;>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Mon, Dec 19, 2016 at 7:53 PM, Dmitriy Setrakyan <
> >>>>>>>>>>>> dsetrak...@apache.org>
> >>>
led benchmarks)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Dec 19, 2016 at 10:15 PM, Denis Magda <
>>>>>> dma...@apache.org
>>>>>>>>>
>>>>
gt;>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Yardstick requires own scripts/configurations (/bin,
> /config,
> >>>>>>> /libs)
> >>>>>>>>>>>> and
&g
gt; creates work/logs directory under yardstick root.
>>>>>> "libs/optional"
>>>>>>> is
>>>>>>>>>>>> for
>>>>>>>>>>>>>>> optional modules but in general we can't say that for
>>&
would be against using libs/optional or libs/ folder for
>>>>> anything
>>>>>>>>>>>>>> benchmark related. I am also against adding any yardstick
>>>>> libraries
>>>>>>>>>>>> without
>>>>>&g
;>>
>>>>>>>>>>>> D.
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Dec 19, 2016 at 8:11 AM, Denis Magda <
>> dma...@apache.org>
>>>>>>>>>> wrote:
>>>>>>&g
down to the implementation.
> >>>>>>>>>>
> >>>>>>>>>> —
> >>>>>>>>>> Denis
> >>>>>>>>>>
> >>>>>>>>>>> On Dec 19, 2016, at 1:10 AM, Serg
>>>>> Hi
>>>>>>>>>>>
>>>>>>>>>>> What's about to introduce the new root folder called 'extras'
>>> with
>>>>>>>>>>> subfolder 'ignite-yardstick' and put there yardstick binaries?
stick' and put there yardstick binaries?
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> On Sun, Dec 18, 2016 at 10:02 PM, Denis Magda <dma...@apache.org
>> >
>> >>>>>> wro
t;>> https://issues.apache.org/
> >>>>>>>>> jira/browse/IGNITE-4212).
> >>>>>>>>>
> >>>>>>>>> The whole purpose of the ticket is to automate benchmarks
> >> execution
> >>>>>&g
the ticket is to automate benchmarks
>> execution
>>>>>> for
>>>>>>>>> the end user for a specific Ignite release. Now he/she needs to go
>>>>>>> through
>>>>>>>>> a number of steps like build, configure, run strictly following
>
script
> >> needs
> >> >>>>> benchmarks' lib which makes sense to put under “libs/optional”
> >> folder.
> >> >>>>>
> >> >>>>> If someone wants to modify the source of an existed benchmark or
> >> add a
> &
k or
>> add a
>> >>> new
>> >>>>> one then he/she needs to follow existed Yardstick guidance. So, no
>> >> need
>> >>> to
>> >>>>> release benchmarks’s sources as a part of Ignite release.
>> >>>>&g
t;>>> release benchmarks’s sources as a part of Ignite release.
> >>>>>
> >>>>> —
> >>>>> Denis
> >>>>>
> >>>>>> On Dec 18, 2016, at 7:08 AM, Dmitriy Setrakyan <
> >> dsetrak...@apache.o
; wrote:
>>>>>>
>>>>>> On Sun, Dec 18, 2016 at 2:53 AM, Oleg Ostanin <oosta...@gridgain.com
>>>
>>>>> wrote:
>>>>>>
>>>>>>> Dmitriy, ignite-yardstick allows user to run plenty of useful
>>
;>>>>>
>>>>>>> On Dec 18, 2016, at 7:08 AM, Dmitriy Setrakyan <
>> dsetrak...@apache.org>
>>>>>> wrote:
>>>>>>>
>>>>>>> On Sun, Dec 18, 2016 at 2:53 AM, Oleg Ostanin <oosta...@gridgain.com
&g
6 at 2:53 AM, Oleg Ostanin <oosta...@gridgain.com
> >
> > >> wrote:
> > >>>
> > >>>> Dmitriy, ignite-yardstick allows user to run plenty of useful
> > Yardstick
> > >>>> benchmarks, which can be used to check Ignite performance
;>>> wrote:
> >>>>>
> >>>>>> Dmitriy, ignite-yardstick allows user to run plenty of useful
> >> Yardstick
> >>>>>> benchmarks, which can be used to check Ignite performance.
> >>>>>>
> >>>&g
enty of useful
>> Yardstick
>>>>>> benchmarks, which can be used to check Ignite performance.
>>>>>>
>>>>>
>>>>> In that case, why would it be under the "libs" folder at all? Do we
>>>> really
>>
s, which can be used to check Ignite performance.
> >>>>
> >>>
> >>> In that case, why would it be under the "libs" folder at all? Do we
> >> really
> >>> need to include benchmarks into Ignite? If yes, then I would create a
> >>&g
uot;libs" folder at all? Do we
>> really
>>> need to include benchmarks into Ignite? If yes, then I would create a
>>> benchmarks folder under "examples" and add all the benchmarks there.
>>>
>>>
>>>>
>>>> On Fri, Dec 16,
.org
>>>
>> wrote:
>>
>>> Oleg, what does ignite-yardstick module do?
>>>
>>> On Fri, Dec 16, 2016 at 12:37 AM, Oleg Ostanin <oosta...@gridgain.com>
>>> wrote:
>>>
>>>> Hello Igniters!
>>>> I'm working
> > >
> > wrote:
> >
> > > Oleg, what does ignite-yardstick module do?
> > >
> > > On Fri, Dec 16, 2016 at 12:37 AM, Oleg Ostanin <oosta...@gridgain.com>
> > > wrote:
> > >
> > > > Hello Igniters!
> > > &
, what does ignite-yardstick module do?
> >
> > On Fri, Dec 16, 2016 at 12:37 AM, Oleg Ostanin <oosta...@gridgain.com>
> > wrote:
> >
> > > Hello Igniters!
> > > I'm working on ticket IGNITE-4212 "Ignite Benchmarking Simplification
> a
016 at 12:37 AM, Oleg Ostanin <oosta...@gridgain.com>
> wrote:
>
> > Hello Igniters!
> > I'm working on ticket IGNITE-4212 "Ignite Benchmarking Simplification and
> > Automation" and I'd like to ask your opinion about ignite-yardstick:
> where
> &
Oleg, what does ignite-yardstick module do?
On Fri, Dec 16, 2016 at 12:37 AM, Oleg Ostanin <oosta...@gridgain.com>
wrote:
> Hello Igniters!
> I'm working on ticket IGNITE-4212 "Ignite Benchmarking Simplification and
> Automation" and I'd like to ask your opinion abou
to the script and script will launch it.
—
Denis
> On Dec 16, 2016, at 12:37 AM, Oleg Ostanin <oosta...@gridgain.com> wrote:
>
> Hello Igniters!
> I'm working on ticket IGNITE-4212 "Ignite Benchmarking Simplification and
> Automation" and I'd like to ask your opinion about i
Hello Igniters!
I'm working on ticket IGNITE-4212 "Ignite Benchmarking Simplification and
Automation" and I'd like to ask your opinion about ignite-yardstick: where
do you think is the most appropriate place to put a compiled
ignite-yardstick module in the apache-ignite binary assembly?
Denis Magda created IGNITE-4212:
---
Summary: Ignite Benchmarking Simplification and Automation
Key: IGNITE-4212
URL: https://issues.apache.org/jira/browse/IGNITE-4212
Project: Ignite
Issue Type
33 matches
Mail list logo
