Evgeniy, AFAIK YCSB is used for NoSQL database benchmark, right? This is not exactly our case, because we are going to test pure SQL.
On Tue, Jan 31, 2017 at 10:55 AM, Evgeniy Stanilovskiy < stanilov...@gmail.com> wrote: > Sergey, did you take a look into https://en.wikipedia.org/wiki/YCSB ? > https://github.com/joshwilliams/YCSB > there is simple jdbc connector looks like it would be ok for us ? > > > Hi, >> >> That’s true that the utility/testing framework needs to be as flexible as >> possible. If the community can’t reuse an existing one let’s make it up. >> >> As for VoltDB SQL Coverage Suite, if it’s Python based then can we >> implement those Python APIs directly calling Ignite.C++? >> >> — >> Denis >> >> On Jan 30, 2017, at 4:39 AM, Sergey Kozlov <skoz...@gridgain.com> wrote: >>> >>> Alexey, I suppose that it's a hard way to do that and at least see a few >>> disadvantages below: >>> >>> 1. The VoltDB has no multithreaded mode. It means huge execution time >>> consumption (say we talk about thousands statement multiplied on caches >>> count, it's the millions of queries). >>> 2. We should add support of Ignite. >>> 3. We should add support of H2 as base engine for us (MySQL/Postgress >>> have >>> less priority) >>> 4. They run it under Jenkins so we need to integrate it with TC somehow. >>> >>> From my standpoint better to make the utility in Ignite than spending >>> time >>> and efforts to adopt an existing tool. At least we have good (or even >>> best) >>> Java experts/developers in community and the task doesn't look a complex >>> one. >>> >>> >>> On Mon, Jan 30, 2017 at 2:58 PM, Alexey Kuznetsov <akuznet...@apache.org >>> > >>> wrote: >>> >>> Sergey, >>>> >>>> Could we use http://www.jython.org/ to make it works as-is? >>>> >>>> On Mon, Jan 30, 2017 at 6:06 PM, Sergey Kozlov <skoz...@gridgain.com> >>>> wrote: >>>> >>>> Hi >>>>> >>>>> Hi reviewed the links below (thanks for Vova Ozerov to pointing me) and >>>>> found that the provided solution is really excellent! >>>>> Unfortunately we can't use it as is (from my standpoint) due lacks of >>>>> Python support in Ignite but we can re-use that idea for Ignite and >>>>> make >>>>> SQL combinations coverage significantly better. >>>>> >>>>> I filed the ticket IGNITE-4627 Tester for SQL functionality >>>>> <https://issues.apache.org/jira/browse/IGNITE-4627> >>>>> >>>>> Please share your thoughts and ideas. >>>>> >>>>> [1] https://www.voltdb.com/blog/testing-voltdb-sqlcoverage >>>>> [2] https://github.com/VoltDB/voltdb/tree/master/tests/sqlcoverage >>>>> >>>>> -- >>>>> Sergey Kozlov >>>>> www.gridgain.com >>>>> >>>>> >>>> >>>> >>>> -- >>>> Alexey Kuznetsov >>>> >>>> >>> >>> >>> -- >>> Sergey Kozlov >>> GridGain Systems >>> www.gridgain.com >>> >>
