Yes, I hear you. TPC's usual mode of operation has been to release details after the benchmark is complete. But TPC does have a policy clause that allows publication of draft specifications to get public feedback before the benchmark is complete. Our 2012 TPC TC paper will have a lot of the high level details. We need to see if we can use the draft clause to also release beta versions of code. Thanks, Reza > -----Original Message----- > From: Craig Ringer [mailto:ringerc@xxxxxxxxxxxxx] > Sent: Thursday, July 05, 2012 8:41 PM > To: Reza Taheri > Cc: Greg Smith; pgsql-performance@xxxxxxxxxxxxxx > Subject: Re: Introducing the TPC-V benchmark, and its > relationship to PostgreSQL > > On 07/06/2012 11:22 AM, Reza Taheri wrote: > > Hi Greg, > > Yes, a single-instance benchmark is a natural fall-out from the TPC-V kit. > Our coding team (4 people working directly on the benchmark with another > 3-4 folks helping in various consulting capacities) is tasked with creating a > multi-VM benchmark. The benchmark is still missing the critical Market > Exchange Emulator function. Once that's done, it would be natural for > someone else in the TPC to take our working prototype and simplify it for a > single-system, TPC-E (not V) reference kit. The conversion is not technically > difficult, but releasing kits is a new path for the TPC, and will take some > work. > Please consider releasing sample versions early in the process, especially as > such releases are new to the TPC. Giving others the opportunity to > contribute different skill sets and experiences before everything is locked > in to the final configuration is important, especially when trying new things. > > -- > Craig Ringer -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
