You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/03/02 00:15:18 UTC
[jira] [Updated] (CALCITE-1118) "noop" JDBC driver for
benchmarking/testing Avatica
[ https://issues.apache.org/jira/browse/CALCITE-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated CALCITE-1118:
--------------------------------
Description:
As I was working on the general effort of improving performance of Avatica (alluded to in CALCITE-1117), I found myself lamenting a view into the performance of Avatica that wasn't bound by the underlying database being written to.
I hacked together a really quick/dirty JDBC driver that does nothing whenever you call the methods (sans creating Statements and DatabaseMetaData instances). Turns out this was really useful in testing our *just* Avatica.
I'm sure there are issues with it, but it was sufficient for doing some write-heavy testing. Would be nice to have it included for future testing.
was:
As I was working on the general effort of improving performance of Avatica, I found myself lamenting a view into the performance of Avatica that wasn't bound by the underlying database being written to.
I hacked together a really quick/dirty JDBC driver that does nothing whenever you call the methods (sans creating Statements and DatabaseMetaData instances). Turns out this was really useful in testing our *just* Avatica.
I'm sure there are issues with it, but it was sufficient for doing some write-heavy testing. Would be nice to have it included for future testing.
> "noop" JDBC driver for benchmarking/testing Avatica
> ---------------------------------------------------
>
> Key: CALCITE-1118
> URL: https://issues.apache.org/jira/browse/CALCITE-1118
> Project: Calcite
> Issue Type: Sub-task
> Components: avatica
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: next
>
>
> As I was working on the general effort of improving performance of Avatica (alluded to in CALCITE-1117), I found myself lamenting a view into the performance of Avatica that wasn't bound by the underlying database being written to.
> I hacked together a really quick/dirty JDBC driver that does nothing whenever you call the methods (sans creating Statements and DatabaseMetaData instances). Turns out this was really useful in testing our *just* Avatica.
> I'm sure there are issues with it, but it was sufficient for doing some write-heavy testing. Would be nice to have it included for future testing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)