Re: [DISCUSS] Apache AGE 0.6.0 Release

2021-09-10 Thread Muhammad Shoaib
Looks gokd to me +1 On Sat, Sep 11, 2021, 08:28 John Gemignani wrote: > Looks good to me. > > +1 > > On Fri, Sep 10, 2021 at 9:52 AM Josh Innis wrote: > > > Dear Apache Community, > > > > > > > > We would like to discuss the Apache AGE release 0.6.0. that we have been > > working toward it. >

Re: [DISCUSS] Apache AGE 0.6.0 Release

2021-09-10 Thread John Gemignani
Looks good to me. +1 On Fri, Sep 10, 2021 at 9:52 AM Josh Innis wrote: > Dear Apache Community, > > > > We would like to discuss the Apache AGE release 0.6.0. that we have been > working toward it. > > > > To learn more about Apache AGE, please see http://age.apache.org/ > > > >

Re: Benchmarking result

2021-09-10 Thread Joe Fagan
Great Josh. I learnt loads reading your script On Fri, 10 Sep 2021 at 18:14, Josh Innis wrote: > Good Job Viet. I made some modifications to the SQL function that you > made. This may be a way to analyze how long it takes to run the queries in > a purely postgres way that only calls explain

Re: Benchmarking result

2021-09-10 Thread Josh Innis
Good Job Viet. I made some modifications to the SQL function that you made. This may be a way to analyze how long it takes to run the queries in a purely postgres way that only calls explain analyze once. SET search_path TO ag_catalog; LOAD 'age'; SELECT create_graph('test_graph'); CREATE OR

[DISCUSS] Apache AGE 0.6.0 Release

2021-09-10 Thread Josh Innis
Dear Apache Community, We would like to discuss the Apache AGE release 0.6.0. that we have been working toward it. To learn more about Apache AGE, please see http://age.apache.org/ Functionalities included and addressed in this release: - Add VLE SRF (Set Returning Function). -

Re: Benchmarking result

2021-09-10 Thread John Gemignani
Good job! On Thu, Sep 9, 2021 at 9:11 PM VUONG QUOC Viet wrote: > Hi Joe and Muhammad, > > I've finished the benchmarking experiments after listening to Muhammad's > suggestions to improve the process: 1. to create 2 separate repos for > original code and optimized code and 2. place the