.
Also, you can use dedicated AWS instances for benchmarking.
Pay attention to the fact that sometimes our benchmarks can show unstable
results in case of
non-dedicated instances.
2018-08-09 21:09 GMT+03:00 Vyacheslav Daradur :
> Huge +1, for a public benchmarking tool and the Docker ba
Vinogradov :
> Igniters,
>
> All critical code changes should be covered by benchmarks.
> Currently, community have no dedicated benchmarking service.
>
> Everyone can run yandstick locally, but this seems to be useless.
> You have to run cluster on 4 clients and 4 servers, at
Igniters,
All critical code changes should be covered by benchmarks.
Currently, community have no dedicated benchmarking service.
Everyone can run yandstick locally, but this seems to be useless.
You have to run cluster on 4 clients and 4 servers, at least.
Currently it is not possible for me
the moment of writing.
On Sat, Sep 16, 2017 at 12:06 AM, Dmitriy Setrakyan
<dsetrak...@apache.org> wrote:
> Cos,
>
> I think Apache BigTop is using servers provided by Amazon. Can you make a
> suggestion on how can Ignite community get a few servers from Amazon for
> benchmarking as
Cos,
I think Apache BigTop is using servers provided by Amazon. Can you make a
suggestion on how can Ignite community get a few servers from Amazon for
benchmarking as well?
D.
On Fri, Sep 15, 2017 at 5:57 AM, Anton Vinogradov <a...@apache.org> wrote:
> Guys,
>
> I fully agree
specific number for
> benchmarking.
>
> Can we start from reference hardware configuration: Num of CPU, RAM and
> HDD(SDD?) configuration, network configs, etc.
>
> Can someone share that kind of knowledge - Which hardware is best for
> Ignite benchmarking?
>
> I found some number
Hello, Dmitriy.
I think experienced members of community have specific number for
benchmarking.
Can we start from reference hardware configuration: Num of CPU, RAM and
HDD(SDD?) configuration, network configs, etc.
Can someone share that kind of knowledge - Which hardware is best
Alexey, I completely agree. However, for the benchmarks to be useful, then
need to be run on the same hardware all the time. Apache Ignite does not
have servers sitting around, available to run the benchmarks.
Would be nice to see how other projects address it. Can Amazon donate
servers for the
Hi, Igniters.
Recently I’ve done some research in benchmarks for Ignite, and noticed that we
don’t have any rules for running benchmarks and collecting result from them.
Although sometimes we have tasks, which results need to be measured. I propose
to formalize such things as:
* set of
look bad. Also,
benchmarking is a very common topic during evaluation process and deserves
a spot up top. I would still place it under Basic Concepts for now. You can
always move it to a separate section once we have more content.
setrak...@apache.org> wrote:
>
> Several comments:
> I would place this page directly under the top Basic Concepts section
> I would rename the link to Benchmarking (performance is assumed)
> I would add a few benchmark runs with examples graphs there
> D.
>
> On Mon, Sep
Several comments:
1. I would place this page directly under the top Basic Concepts section
2. I would rename the link to Benchmarking (performance is assumed)
3. I would add a few benchmark runs with examples graphs there
D.
On Mon, Sep 11, 2017 at 5:03 PM, Denis Magda <
I’ve done the primarily review and rename the page address. That’s it:
https://apacheignite.readme.io/docs/perfomance-benchmarking
<https://apacheignite.readme.io/docs/perfomance-benchmarking>
Prachi, please do the final review. The page is already online.
—
Denis
> On Sep 8, 2017, at
Thanks. Here is a direct link on the new page about Ignite Benchmarking(hidden
for now): https://apacheignite.readme.io/v2.1/docs/perfomance-tests. Please
review.
Mostly it was aggregated from the information in the repo
07.09.2017, 20:57, "Dmitriy Setrakyan" <dsetrak...@apache.org
Actually, it can be contributed directly to readme.io. Alexey, I just sent
you an invite.
You can create a new page for benchmarking and make it invisible for now,
while you are working on it. If you need us to review it, please send a
direct link to it here.
D.
On Thu, Sep 7, 2017 at 8:26 AM
any information about Apache Ignite
> benchmarking on our site https://apacheignite.readme.io. I want to add
> such a page, but I can’t find appropriate section for it. I suggest to make
> new section named ‘Tests and Benchmarking’ and put all information about
> benchmaring in sec
Hi, guys.
Issue[1] stated that we have not any information about Apache Ignite
benchmarking on our site https://apacheignite.readme.io. I want to add such a
page, but I can’t find appropriate section for it. I suggest to make new
section named ‘Tests and Benchmarking’ and put all information
Aleksei Zaitsev created IGNITE-6278:
---
Summary: Add benchmarking page to readme.io
Key: IGNITE-6278
URL: https://issues.apache.org/jira/browse/IGNITE-6278
Project: Ignite
Issue Type: Wish
te 1.9 benchmarking purposes.
If you’re happy with it then Oleg is free to merge the changes into 1.9 and
release them there.
—
Denis
> On Feb 10, 2017, at 2:50 AM, Oleg Ostanin <oosta...@gridgain.com> wrote:
>
> I'm sorry, there wasn't any problem with the build, it was local pr
t;>> On Jan 27, 2017, at 2:13 AM, Oleg Ostanin <oosta...@gridgain.com>
>>>> wrote:
>>>> >>>
>>>> >>> Hi!
>>>> >>>
>>>> >>> I've changed the README.txt and DEVNOTES.txt f
DME.txt and DEVNOTES.txt files. Also added a
>>> simple
>>> >>> config file for quick and easy start. Please take a look at them and
>>> tell
>>> >>> me what you think.
>>> >>>
>>> >>> https://github.com/apac
https://github.com/apache/ignite/pull/1471
>> >>>
>> >>> On Wed, Dec 28, 2016 at 8:59 AM, Ilya Suntsov <isunt...@gridgain.com>
>> >> wrote:
>> >>>
>> >>>> Denis,
>> >>>>
>> >>>> I
gt;
> >>>> Denis,
> >>>>
> >>>> I think we can remove all configs except:
> >>>>
> >>>> benchmark-multicast.properties
> >>>>
> >>>> benchmark.properties
> >>>>
> >>
;>>>> - What is the difference between "Building from standalone sources"
>>>> and
>>>>>>>> "Building from Ignite Sources"? In my understanding, a user
>> downloads
>>>>>>>> Apache Ignite release that has all
gt; wrote:
> >>>>>
> >>>>> Hi!
> >>>>>
> >>>>> I've changed the README.txt and DEVNOTES.txt files. Also added a
> simple
> >>>>> config file for quick and easy start. Please take a look at them and
> >
added a simple
>>>>> config file for quick and easy start. Please take a look at them and
>> tell
>>>>> me what you think.
>>>>>
>>>>> https://github.com/apache/ignite/pull/1471
>>>>>
>>>>> On Wed, Dec
; ignite-base-config.xml
>>>>
>>>> ignite-localhost-config.xml
>>>>
>>>> ignite-multicast-config.xml
>>>>
>>>> 2016-12-28 2:49 GMT+03:00 Denis Magda <dma...@apache.org>:
>>>>
>>>>> I would h
ml
>>
>> ignite-localhost-config.xml
>>
>> ignite-multicast-config.xml
>>
>> 2016-12-28 2:49 GMT+03:00 Denis Magda <dma...@apache.org>:
>>
>>> I would have only those configs that are useful. Ilya Suntsov, basing on
>>> your ex
re useful. Ilya Suntsov, basing on
> your experience, please suggest which configs makes sense to include into
> every Ignite release.
>
> Oleg, also please note that community decided to include not only the
> benchmarking binaries but the sources as well into every Apache Ignit
I would have only those configs that are useful. Ilya Suntsov, basing on your
experience, please suggest which configs makes sense to include into every
Ignite release.
Oleg, also please note that community decided to include not only the
benchmarking binaries but the sources as well
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
Github user ilantukh closed the pull request at:
https://github.com/apache/ignite/pull/592
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/592
GG-10988 benchmarking
This version uses CHM8 instead of JDK CHM.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilantukh/ignite ignite-gg
53 matches
Mail list logo
