Dmitriy Examples folder is not good location for yardstick binaries (but good for yardstick sources). I suppose we should look on how to other products include additional tools.
On Sun, Dec 18, 2016 at 6:08 PM, Dmitriy Setrakyan <dsetrak...@apache.org> 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 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 > 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, 2016 at 11:49 PM, Dmitriy Setrakyan < > dsetrak...@apache.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 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? We can > > put > > > it > > > > in the libs/optional along with an others optional libraries, or we > can > > > > create a new directory named "tools" in the root directory and put > > > > "ignite-yardstick" in it, or we can find another solution. > > > > > > > > Best regards > > > > Oleg > > > > > > > > > > -- Sergey Kozlov GridGain Systems www.gridgain.com
