On Thu, Aug 18, 2016 at 5:54 PM, James Taylor <jamestay...@apache.org> wrote:
> The data loaded fine for us. Mind describing what you did to get it to work and with what versions and configurations and with what TPC loading and how much of the workload was supported? Was it a one-off project? > If TPC is not representative of real > workloads, I'm not sure there's value in spending a lot of time running > them. I suppose the project could just ignore TPC but I'd suggest that Phoenix put up a page explaining why TPC does not apply if this the case; i.e. it is not representative of Phoenix work loads. When people see that Phoenix is for "OLTP and analytical queries", they probably think the TPC loadings will just work given their standing in the industry. Putting up a disavowal with explanation will save folks time trying to make it work and it can also be cited when folks try to run TPC against Phoenix and they have a bad experience, say bad performance. On the other hand, even if an artificial loading, unless Phoenix has a better means of verifying all works, I'd think it would be a useful test to run before release or on a nightly basis verifying no regression in performance or in utility. Thanks, St.Ack > Thanks, > James > > On Thu, Aug 18, 2016 at 5:36 PM, Stack <st...@duboce.net> wrote: > > > On Thu, Aug 18, 2016 at 3:00 PM, James Taylor <jamestay...@apache.org> > > wrote: > > > > > On Thu, Aug 18, 2016 at 10:48 AM, Stack <st...@duboce.net> wrote: > > > > > ... > > > > > I'm not sure how the TCP benchmarks map to the real world use > > > cases of our user community. > > > > > > I'd think the TPC loadings would be worth nailing since thats how the > > engines get compared. If it is true Phoenix falters loading the dataset, > > that doesn't look good. If Phoenix is punting on TPC, that'd be good to > > know too. > > > > Thanks, > > St.Ack > > >
